Snapcraft can't be run against a local or remote LXD project
Metadata
Current evaluation
Feature request from the LXD maintainer for snapcraft to support LXD projects (local/remote) for isolated or cluster-based builds. ~6 years old, no labels, zero comments, no maintainer response. Overlaps with remote LXD work tracked in snapcraft#4454.
Suggested action: close stale
Reason: The issue has had zero comments, no labels, and no maintainer interaction for ~6 years, and the author himself suggested merging it into the remote LXD builds effort, which is actively triaged and tracked in snapcraft#4454 (Jira CRAFT-2554, with discussion moved to craft-providers#508). Closing it as subsumed by that tracked effort avoids duplicate tracking of the same LXD integration work.
Impact:
30
Quick Win:
13.5
Staleness:
95
Complexity:
55
Confidence:
70
Support Request:
10
Issue body
As we are ramping up the push for users to create and utilize LXD projects[1], either locally to isolate users on a multi-user machine or remotely to run a company-wide cluster, it would be great for snapcraft to understand those and let you use them.
This probably ties into remote builds to LXD to an extent so you may want to merge this in that effort.
The reason for me bringing this up is that we're now testing a shared LXD cluster with various users (Canonical employees, see ~lxd-test-cluster) and it'd be nice to be able to build snaps on it.
References:
[1] https://linuxcontainers.org/lxd/docs/master/projects
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
13.5
Staleness:
95
Complexity:
55
Confidence:
70
Support Request:
10
|
close stale | Feature request from the LXD maintainer for snapcraft to support LXD projects (local/remote) for isolated or cluster-based builds. ~6 years old, no labels, zero comments, no maintainer response. Overlaps with remote LXD work tracked in snapcraft#4454. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | Feature request to enable snapcraft to use local or remote LXD projects for build isolation and clustering. Open for nearly six years with zero maintainer interaction or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
80
Support Request:
10
|
needs triage | Feature request to add LXD project support to snapcraft for local isolation and remote clusters. Untriaged and inactive for nearly six years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
60
Confidence:
90
Support Request:
10
|
close stale | Feature request to support local or remote LXD projects in snapcraft. Open for over 5 years with no maintainer response, comments, or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
30
Confidence:
90
Support Request:
5
|
needs triage | Feature request to enable snapcraft to build against local or remote LXD projects. Unlabelled and unacknowledged by maintainers for over five years with zero comments. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft#4454
(confidence 75%)
Open, triaged feature request for remote LXD instances (Jira CRAFT-2554, follow-up in craft-providers#508); the author of this issue suggested merging this request into that same effort.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4454 Allow snapcraft to use remote lxd instances. | snapcraft | open | Feature request to let snapcraft build against a remote LXD instance (via lxc remote config) instead of requiring a local LXD install, enabling snap development on macOS/Windows. Triaged and tracked in Jira (CRAFT-2554); follow-up discussion moved to craft-providers#508, which remains open. | |
| #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. | |
| #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. | |
| #1795827 Snapcraft doesn't install snapcraft inside the lxd container | snapcraft (launchpad) | open | Snapcraft's LXD build provider failed to install the snapcraft snap inside the container, leaving 'snapcraft: not found'. Reported ~8 years ago with no maintainer interaction; the provider code has since been heavily refactored (craft-providers integration). | |
| #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. | |
| #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. | |
| #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. | |
| #1892551 snapcraft fails to run if it is installed as a try snap | snapcraft (launchpad) | open | Snapcraft 4.x fails when installed via 'snap try': the LXD build provider tries to download the host snapcraft snap file from snapd, which returns 400 for try snaps. Unlabelled, 0 comments, ~6 years old, never triaged. | |
| #1697979 snapcraft fails on initial cleanbuild probe | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft cleanbuild failed due to LXD connection errors when LXD was provided via a third-party snap alias. The report received no comments or fixes and was abandoned. | |
| #1822372 Snapcraft cleanbuild on Arch Linux with LXD - AppArmor permission error | snapcraft (launchpad) | closed | Closed without resolution due to prolonged inactivity. The report detailed an AppArmor permission error during snapcraft cleanbuild on Arch Linux with LXD. No comments or fixes were provided, indicating the issue was abandoned or marked as invalid. |