Unable to build with lxd when using lxd with lvm pool.
Metadata
Current evaluation
Snapcraft 3.8/3.9.2 fails with --use-lxd when LXD uses a custom LVM pool, due to a hardcoded /var/snap/lxd/common path. 6+ years old, no labels, no maintainer interaction, no comments.
Suggested action: close stale
Reason: The issue is 2488 days (~6.8 years) old with zero comments, no labels, and no maintainer interaction. It references snapcraft 3.8/3.9.2 on Ubuntu 18.04, both of which are long since EOL. The current codebase has been substantially restructured (snapcraft/ now has services/, models/, parts/ subdirectories), making it very likely the LXD integration code has been rewritten. The hardcoded path issue described is almost certainly no longer present in the current version. The issue is both inactive and no longer relevant to the current codebase.
Impact:
30
Quick Win:
18.0
Staleness:
95
Complexity:
40
Confidence:
70
Support Request:
15
Issue body
System version: ubuntu 18.04
snapcraft: 3.8(3440) and 3.9.2(3720)
When tring to build snaps with --use-lxd, the following error is shown:
/snap/snapcraft/3440/lib/python3.5/site-packages/pylxd/models/_model.py:116: UserWarning: Attempted to set unknown attribute "type" on instance of "Container"
key, self.__class__.__name__
Stopped
An error occurred with the instance when trying to start with 'LXD': Common start logic: No such file or directory: "/var/snap/lxd/common/lxd/storage-pools/pool1/containers/snapcraft-project/rootfs".
Ensure that 'LXD' is setup correctly and try again.
It seems that the directory is hardcoded toward the /var directory which is the default one I believe.
My lxd is setup with a lvm pool manually.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18.0
Staleness:
95
Complexity:
40
Confidence:
70
Support Request:
15
|
close stale | Snapcraft 3.8/3.9.2 fails with --use-lxd when LXD uses a custom LVM pool, due to a hardcoded /var/snap/lxd/common path. 6+ years old, no labels, no maintainer interaction, no comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
20
|
close stale | Build fails with LXD when using a custom LVM pool due to a hardcoded path error. Issue is 6+ years old with no maintainer interaction or updates. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
95
Support Request:
20
|
close stale | Snapcraft fails to detect custom LVM storage pools when building with LXD on Ubuntu 18.04. No activity for over 6 years; affected versions are EOL. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
25
Confidence:
95
Support Request:
30
|
close stale | Snapcraft fails to start LXD containers when using a custom LVM storage pool due to a hardcoded path. Issue is over 6 years old with no activity. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
92
Support Request:
10
|
close stale | Snapcraft build fails with LXD when using a custom LVM storage pool. Issue is inactive for over six years with no maintainer response or labels. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1825820 Snapcraft doesn't update the `snapcraft-project` disk source when the path is moved | snapcraft (launchpad) | open | 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. | |
| #1865230 snapcraft --use-lxd should have message about requring sudo | snapcraft (launchpad) | open | snapcraft 3.x --use-lxd (LXD provider, a technology preview) left LXD in a broken state when run without sudo; reporter suggests failing early. 6.5 years old, zero comments, no labels or maintainer interaction; LXD preview since superseded by Multipass. | |
| #1746612 Snapcraft cleanbuild doesn't work if you're not using the LXD snap | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft hardcodes the LXD snap path during cleanbuild, causing failures with deb-installed LXD. The report appears abandoned or superseded by updated Snapcraft versions that dynamically detect LXD installations. | |
| #1752498 cleanbuild fails with lxd snap | snapcraft (launchpad) | closed | A user reported snapcraft cleanbuild failing with the LXD snap due to a FUSE mount permission error inside the container. With zero comments and years of inactivity, the report was abandoned and closed without a fix or resolution. | |
| #1839399 snapcraft not pulling snap from lxd container | snapcraft (launchpad) | open | 2019 report that snapcraft 3.7.1 with --use-lxd built a snap inside the LXD container but never copied it back to the host. No labels, no maintainer interaction, 7 years old; the LXD provider has since been rewritten via craft-providers. | |
| #1666735 snapcraft cleanbuild does not work with lxd installed via snap | snapcraft (launchpad) | closed | Closed without resolution or merge. The report notes snapcraft cleanbuild fails to detect LXD installed via snap, suggesting checks via snap list or lxc list instead of apt cache. No fix was implemented or documented. | |
| #1814928 Can't build a Snap program using lxd | snapcraft (launchpad) | closed | Closed without resolution. LXD containers cannot access the msr module required for Snap builds, rendering the guide unworkable. No fix or workaround was provided. |