`--workdir` is ignored
Metadata
Current evaluation
Reporter: --workdir ignored by snapcraft-rocks containers; only /project works. Full docker repro given. Doc gap conceded by reporter, but why custom dirs are rejected (entrypoint/pwdb) is still unconfirmed. No maintainer response.
Suggested action: needs triage
Reason: The issue carries no labels, no assignee, and no maintainer response; the only comment is the reporter's own, so it has never been assessed by a maintainer, which is the definition of needs_triage. Impact is modest rather than high because a documented workaround exists: upstream snapcraft/docker/README.md documents `-v \`pwd\`:/project ghcr.io/canonical/snapcraft:8_core24`, and the reporter himself confirmed the doc half is answered, leaving only the open question of why --workdir is rejected. Confidence is held down because the core22-8 branch holding rockcraft.yaml and the wrapper script is not present in the available mirror, so I could not locate the entrypoint that hardcodes /project, confirm whether a fix has since landed, or distinguish a rockcraft-side regression from expected pebble behaviour.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
11
Complexity:
35
Confidence:
48
Actionability:
55
|
needs triage | Reporter: --workdir ignored by snapcraft-rocks containers; only /project works. Full docker repro given. Doc gap conceded by reporter, but why custom dirs are rejected (entrypoint/pwdb) is still unconfirmed. No maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
14
Complexity:
20
Confidence:
70
Actionability:
60
|
needs triage | User reports --workdir flag is ignored in snapcraft docker container; discovered workaround is using /project instead. Issue lacks labels and maintainer response after 873 days. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14
Staleness:
85
Complexity:
30
Confidence:
60
Support Request:
65
|
needs triage | Reporter found snapcraft rock ignores --workdir and requires project mounted at /project; self-resolved that /project is documented in README but not the announcement, leaving an open question on why a custom workdir cannot be used. No maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
80
Support Request:
20
|
close stale | --workdir flag ignored in snapcraft Docker container; author found workaround using /project but original behavior remains unresolved. No maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
20
Confidence:
75
Support Request:
30
|
needs triage | Report that --workdir flag is ignored in snapcraft Docker image, forcing usage of /project instead. Unlabelled, inactive for over two years, author noted workaround but question remains open. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #60 Set `WORKDIR /workdir` on Docker level | snapcraft-rocks | open | Feature request to set Docker WORKDIR to /workdir as a base-image convention for snapcraft rocks. Discussed by maintainers, who are skeptical (GH search shows /app far more common); no agreement or implementation. |