Snapcraft doesn't update the `snapcraft-project` disk source when the path is moved
Metadata
Current evaluation
LXD builds reportedly fail after moving a project because the instance retains the old disk source. LXD remains supported, but this untriaged report needs verification against the current craft-providers integration.
Suggested action: needs triage
Reason: The body provides an exact three-step reproducer and a concrete missing-source error, but the report has no labels, assignee, or maintainer response. Current code still supports LXD and passes the current absolute project path to launched_environment before mounting it in prepare_instance; the old snapcraft-project literal is absent, so current-version behavior and craft-providers handling must be verified before deciding whether it is fixed.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
13
Complexity:
55
Confidence:
80
Actionability:
68
Issue body
Bug reproduce instructions
--------------------------
1. Run `snapcraft --use-lxd` in one project
1. Move the project directory to another path
1. Re-run `snapcraft --use-lxd`
Current behavior
-----------------
Snapcraft errors with:
```
An error occurred with the instance when trying to start with 'LXD': Common start logic: Missing source '/home/brlin/工作空間/個人專案/Unofficial Snap Packaging for waifu2x' for disk 'snapcraft-project'.
Ensure that 'LXD' is setup correctly and try again.
```
Expected behavior
------------------
Snapcraft should check the project directory path, and if it's changed, update the `snapcraft-project` disk source path
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
13
Complexity:
55
Confidence:
80
Actionability:
68
|
needs triage | LXD builds reportedly fail after moving a project because the instance retains the old disk source. LXD remains supported, but this untriaged report needs verification against the current craft-providers integration. | |
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
18
Complexity:
45
Confidence:
90
Actionability:
82
|
needs triage | LXD builds fail after moving a project because the LXD disk source retains the old path; the subsystem remains present, but this untriaged report needs current-version verification. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
12
Staleness:
95
Complexity:
40
Confidence:
60
Support Request:
10
|
close stale | Snapcraft --use-lxd fails after moving the project directory because the LXD disk source 'snapcraft-project' still points at the old path. Open ~7.4 years with no labels, comments, or maintainer interaction; LXD build support has since been removed from snapcraft. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
5
|
close stale | Snapcraft fails to update the LXD disk source path when a project directory is moved, causing build errors. The issue has been open for over 7 years with no maintainer interaction or updates. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
10
|
close stale | Snapcraft fails when the project directory is moved because LXD retains the old snapcraft-project disk source path. Untriaged, inactive for over 7 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Snapcraft fails to update the LXD disk source path after a project directory is moved, causing startup errors. Issue is unlabelled, has zero comments, and has been inactive for over 7 years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1795827 Snapcraft doesn't install snapcraft inside the lxd container | snapcraft (launchpad) | open | Historical LXD builds failed because Snapcraft was not injected into the container; the modern Craft Providers LXD path injects Snapcraft and resolves the legacy failure. | |
| #1839399 snapcraft not pulling snap from lxd container | snapcraft (launchpad) | open | Snapcraft 3.7.1 reported a successful --use-lxd build but left the generated snap absent on the host; a maintainer identified possible CWD handling, and the case remains unresolved. | |
| #1896820 Snapcraft can't be run against a local or remote LXD project | snapcraft (launchpad) | open | Support user-selected local and remote LXD projects is still pending; Snapcraft hard-codes its own local LXD project, while remote-instance work is tracked separately. | |
| #1746612 Snapcraft cleanbuild doesn't work if you're not using the LXD snap | snapcraft (launchpad) | closed | Closed after the missing hostfs behavior was fixed upstream in lxc/lxd#4183. Snapcraft PR #1912 offered a workaround but was not merged. | |
| #2014963 Snapcraft fails to build snap if Snapcraft itself is installed using `snap try` | snapcraft (launchpad) | open | `snap try` Snapcraft could not self-inject into legacy LXD builds because snapd cannot download a try snap; the affected provider is removed, but current behavior needs retesting. | |
| #5420 Snapcraft 7 fails to launch a LXD container based on host apt sources entries | snapcraft | closed | Closed as a duplicate of canonical/snapcraft#4408; no separate fix was made for this report. | |
| #1750642 Snapcraft fails in LXD container on Debian 9 | snapcraft (launchpad) | closed | Closed as stale in September 2026 because Debian 9 and the reported Snapcraft version were outdated; no fixing PR or commit was identified. | |
| #1666735 snapcraft cleanbuild does not work with lxd installed via snap | snapcraft (launchpad) | closed | Fixed by merged canonical/snapcraft#1199 (commit 417989880), making cleanbuild LXD detection packaging-independent instead of relying on apt package metadata. | |
| #1992213 Snapcraft crashes when the APT unprivileged user owns the host's source list file instead of root | snapcraft (launchpad) | open | Snapcraft 8187 crashed opening a 0600 _apt-owned APT metadata file. The legacy LXD path was removed, but equivalent current apt-cache checks still need review. | |
| #1851905 Unable to build with lxd when using lxd with lvm pool. | snapcraft (launchpad) | open | Snapcraft 3.8/3.9.2 --use-lxd reportedly assumes a directory-backed LXD pool and fails on LVM pools; the old report has no maintainer triage or follow-up. |