docker run in the tutorial will fail
Metadata
Current evaluation
The Docker command remains unprefixed, but the shared fresh-system setup now grants the user Docker socket access, so the reported failure is resolved.
Suggested action: close resolved
Reason: The shared tutorial setup now runs `sudo adduser $USER docker`, `newgrp docker`, and restarts Docker before users reach the unprefixed hello-world command. This socket-permission remediation is present in the current tree, with commit be7862f8 providing the relevant tutorial setup change.
Evaluated by: mr-cal-bot
Impact:
30
Quick Win:
23
Complexity:
18
Confidence:
97
Actionability:
92
Issue body
### Request type
Fix
### What needs to get done
Hi,
I've ran through your tutorial as I wanted to refer to it for creating a ROCK artifact.
In doing so I realized that the line `docker run --rm hello:latest exec hello -t` will fail on a fresh system.
What will happen is this:
```
docker run --rm hello:latest exec hello -t

docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
: command not found
```
The reason for that are the default permissions:
```
ll /var/run/docker.sock
srw-rw---- 1 root root 0 Jul 24 10:46 /var/run/docker.sock=
```
I like your tutorial and my suggestion would be to not go into socket group management and instead maybe just suggest it with `sudo` as that will allow it to work - WDYT?
```
sudo docker run --rm hello:latest exec hello -t
hello, world
```
### Documentation location
https://documentation.ubuntu.com/rockcraft/en/stable/tutorials/hello-world/
### Additional information
_No response_
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
23
Complexity:
18
Confidence:
97
Actionability:
92
|
close resolved | The Docker command remains unprefixed, but the shared fresh-system setup now grants the user Docker socket access, so the reported failure is resolved. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
22
Complexity:
10
Confidence:
85
Actionability:
80
|
keep open | Tutorial documentation uses docker commands that fail on fresh systems due to socket permissions; suggests adding sudo | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
26
Staleness:
65
Complexity:
15
Confidence:
75
Support Request:
10
|
keep open | Hello-world tutorial docker run command fails on fresh systems due to Docker socket permissions. Acknowledged by maintainer, linked to broader non-root doc testing issue #651. Problem still present in current code. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
15
Confidence:
75
Support Request:
5
|
needs triage | Tutorial command fails due to Docker socket permissions. Contributor suggested sudo. Maintainer linked to broader issue. Lacks labels and has seen no action in over a year, requiring prioritization. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
10
Confidence:
80
Support Request:
10
|
needs triage | Tutorial command fails due to Docker socket permissions; suggests adding sudo. Linked to broader issue #651, awaiting maintainer triage. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
15
Confidence:
75
Support Request:
10
|
close stale | Tutorial command fails due to Docker socket permissions; maintainer acknowledged it as part of a broader issue but it has seen no follow-up or resolution. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/rockcraft#651
(confidence 100%)
A maintainer explicitly linked the broader proposal to run Spread documentation tests as a nonroot user; that regression-test gap remains open.
Related issues
No related issues found above the similarity threshold.