snapcraft not pulling snap from lxd container
Metadata
Current evaluation
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.
Suggested action: close stale
Reason: The report targets snapcraft 3.7.1 (2019) using the --use-lxd flag and the 'technology preview' LXD provider, both of which have been superseded by the craft-providers-based default LXD provider in modern snapcraft, so the affected version is long unsupported and the original problem is no longer reproducible. The issue has had zero comments, no labels, and no maintainer interaction for ~7 years, and the related-issue corpus shows a cluster of similarly abandoned 2018-2019 LXD-provider bugs (e.g. #1890965, closed).
Impact:
15
Quick Win:
8.25
Staleness:
95
Complexity:
45
Confidence:
70
Support Request:
10
Issue body
alan@KinkPad-K450:~/Source/personal/b2$ snapcraft --use-lxd
The LXD provider is offered as a technology preview for early adopters.
The command line interface, container names or lifecycle handling may change in upcoming releases.
Launching a container.
Waiting for cloud-init
status: done
Skipping pull b2 (already ran)
Skipping pull desktop-gtk2 (already ran)
Skipping pull snapcraft-preload (already ran)
Skipping build b2 (already ran)
Skipping build desktop-gtk2 (already ran)
Skipping build snapcraft-preload (already ran)
Skipping stage b2 (already ran)
Skipping stage desktop-gtk2 (already ran)
Skipping stage snapcraft-preload (already ran)
Skipping prime b2 (already ran)
Skipping prime desktop-gtk2 (already ran)
Skipping prime snapcraft-preload (already ran)
The requested action has already been taken. Consider
specifying parts, or clean the steps you want to run again.
Snapping 'b2' -
Snapped b2_9198f33_amd64.snap
alan@KinkPad-K450:~/Source/personal/b2$ ls
snap BBC_owl.svg owl.png
Snap exists in project directory inside the container, but for some reason it never gets pulled to the host.
https://github.com/popey/b2-snap is the project I am using.
This is using snapcraft from candidate, 3.7.1
alan@KinkPad-K450:~$ snapcraft version
snapcraft, version 3.7.1
alan@KinkPad-K450:~$ snap version
snap 2.40
snapd 2.40
series 16
ubuntu 19.04
kernel 5.0.0-23-generic
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
8.25
Staleness:
95
Complexity:
45
Confidence:
70
Support Request:
10
|
close stale | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Bug report from 7 years ago detailing snapcraft failing to copy built snaps from LXD containers to the host. No maintainer interaction or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Report that snapcraft with --use-lxd builds a snap inside the container but fails to copy it back to the host. No maintainer response, reported 7 years ago. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | snapcraft --use-lxd builds a snap inside an LXD container but fails to copy the output to the host. Issue is 7 years old, uses deprecated versions, and lacks maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
25
Confidence:
92
Support Request:
30
|
close stale | Report of snapcraft failing to pull built snaps from LXD containers in version 3.7.1 on Ubuntu 19.04. No maintainer response or activity in over 6 years. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft (launchpad)#1890965
(confidence 55%)
Contemporaneous 'snapcraft --use-lxd is broken' bug from the same 3.x LXD-provider era; closed without a documented fix, indicating the era's LXD issues were superseded by the craft-providers rewrite.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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). | |
| #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. | |
| #1896820 Snapcraft can't be run against a local or remote LXD project | snapcraft (launchpad) | open | 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. | |
| #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. | |
| #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. | |
| #1859469 snapcraft lxd + snapd transition in progress | snapcraft (launchpad) | closed | Closed as non-reproducible and abandoned. The snapcraft lxd command failed due to a snapd transition conflict, but the issue was resolved in version 3.8 and later. | |
| #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. | |
| #1848732 --shell does not make snapcraftctl available | snapcraft (launchpad) | open | 2019 report that `snapcraft pull --use-lxd --shell` leaves `snapcraftctl` unavailable in the LXD shell. No labels, comments, or maintainer activity for about 6 years. snapcraft 2.x/3.x removed snapcraftctl, so the report is outdated. | |
| #1570708 snapcraft should remove lxd container once finished the build | snapcraft (launchpad) | closed | Requested automatic LXD container cleanup after snapcraft cleanbuild was closed without resolution. Zero comments and no implementation indicate the request was abandoned. | |
| #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. |