snapcraft unable to find snap/snapcraft.yaml file
Metadata
Current evaluation
Snapcraft 3.11 on Multipass intermittently lost the project dir in the VM ('Could not find snap/snapcraft.yaml'), only fixable by `snapcraft clean`. Reproducer never supplied; reporter redirected it to the Multipass tracker and never followed up.
Suggested action: close stale
Reason: The report was never made actionable: @cjp256 explicitly asked 'Can you share any other steps you are taking to help reproduce and perhaps even the project itself?' and the author only replied 'Will update this issue if this happen on 1.2.0' — no project, no logs, no repro ever arrived. @sergiusens redirected it to the Multipass tracker ('Can you log an issue on Multipass and reference this bug?'), and the author himself concluded 'its seems like issue about snapcraft and multipass interaction between each other'. The affected code path no longer exists: snapcraft's 3.11-era provider handling was replaced by craft-providers (commit 2980d145c 'providers: use new craft-providers interface'), and Multipass is no longer the default provider on Linux (snapcraft/providers.py now defaults to LXD on Linux, Multipass only as the non-Linux fallback). Closing as stale/abandoned rather than resolved — no fixing commit exists for this symptom in this repo, so a residual risk remains for macOS users, which is why confidence is not high.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
2
Complexity:
72
Confidence:
58
Actionability:
18
|
close stale | Snapcraft 3.11 on Multipass intermittently lost the project dir in the VM ('Could not find snap/snapcraft.yaml'), only fixable by `snapcraft clean`. Reproducer never supplied; reporter redirected it to the Multipass tracker and never followed up. | |
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
2
Complexity:
68
Confidence:
86
Actionability:
18
|
close stale | Snapcraft 3.11/Multipass 1.1 intermittently lost the project manifest; the requested reproducer and Multipass 1.2 follow-up never arrived, and the legacy provider path has been replaced. | |
| stealth/space-bunny-alpha |
Impact:
53
Quick Win:
9
Complexity:
63
Confidence:
67
Actionability:
44
|
needs triage | Legacy Snapcraft 3.11 on Multipass intermittently loses the project mount, reports a missing snapcraft.yaml, and requires a VM-destroying clean; awaiting triage. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
16
Staleness:
98
Complexity:
55
Confidence:
60
Support Request:
10
|
close stale | snapcraft 3.11 (2019) loses snap/snapcraft.yaml after a few builds and drops to the VM shell; workaround is snapcraft clean. 6+ years old, no labels, no maintainer comments, tied to a long-superseded build environment. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
15
|
close stale | Reports a bug where snapcraft fails to locate snapcraft.yaml after a few builds, requiring a clean that recreates the VM. Unaddressed for over six years on an outdated version. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
65
Confidence:
90
Support Request:
10
|
close stale | Reports snapcraft failing to locate snap/snapcraft.yaml after a few builds, requiring VM recreation. Unaddressed for over 6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Reports snapcraft failing to locate snapcraft.yaml after initial builds, dropping to VM shell, and requiring a clean. Issue is over 6 years old with no maintainer response or updates. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Snapcraft fails to locate snap/snapcraft.yaml after a few builds, dropping to VM shell. Requires snapcraft clean to workaround. Untriaged, inactive for over 6 years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft#5145
(confidence 40%)
Also a multipass-provider failure report whose root cause was traced into craft-providers (craft-providers#211), the same subsystem that now owns instance/project mounting; different symptom (launch failure, not missing project dir).
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1806083 snapcraft fails to locate multipass (inside a multipass session) | snapcraft (launchpad) | open | Snapcraft 3.0.1 falsely reported Multipass missing inside a Multipass guest; Darwin-only detection in e9ae8d29f addressed the old path, but the Launchpad record remains open. | |
| #1807125 After snapcraft refresh, old multipass containers no longer work | snapcraft (launchpad) | open | Snapcraft 3.0.1 could reuse incompatible Multipass VMs after a 3.0.0 refresh, causing a misleading missing-project error until snapcraft clean; the report is untriaged. | |
| #5145 snapcraft fails to launch multipass instance when multipass isn't pre-installed | snapcraft | open | Snapcraft emits cryptic 'Remote "snapcraft" is unknown or unreachable / exit code 2' when Multipass can't launch the build instance; maintainer traced it to image-server unavailability or non-amd64 hosts, fix tracked in craft-providers#211 | |
| #1794955 snapcraft erroneously errors when deleting non-existent multipass container | snapcraft (launchpad) | open | snapcraft clean treats an absent Multipass instance as a deletion error after Multipass was reinstalled; the report is concrete but untriaged and may need validation against the current clean path. | |
| #4106 Error 2 on snapcraft on linux with multipass: | snapcraft | closed | Multipass's Snapcraft image remote recovered; CI and the reporter succeeded again, and the reporter closed the report as solved without a Snapcraft code change. | |
| #1810915 snapcraft can't tell when multipass is installed but disabled | snapcraft (launchpad) | open | Snapcraft misclassified an installed but disabled Multipass snap as missing, prompting installation before failing. The 2018 report remains untriaged, and its behavior needs validation against the current provider architecture. | |
| #1813979 snapcraft cleanbuild wants to install multipass but it's already installed | snapcraft (launchpad) | closed | Deb-packaged Snapcraft 2.43.1 failed while Multipass worked in 3.0.1. Legacy cleanbuild was later removed because builds are clean by default. | |
| #1813942 `snapcraft clean <part>` doesn't ensure the project is mounted | snapcraft (launchpad) | open | Snapcraft 3.1 clean <part> fails in Multipass after manually unmounting the project; the report remains unlabelled and untriaged with no activity since submission. | |
| #1947914 concurrent snapcraft builds with multipass provider | snapcraft (launchpad) | open | Snapcraft 5/Core 18 Multipass builds reportedly shared 10.30.202.6 and terminated silently; the old report has no maintainer assessment and needs triage against current versions. | |
| #1794497 Snapcraft can't re-use build VM if anything went wrong with the initial setup | snapcraft (launchpad) | closed | Fixed by the Multipass provider check merged in PR #3381 as commit 51e75b4de. |