snapcraft not pulling snap from lxd container
Metadata
Current evaluation
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.
Suggested action: keep open
Reason: The maintainer explained that the project is mounted into LXD and the snap should therefore be created on the host path, then identified CWD handling as the likely defect. The report includes the command, output, and exact versions, but no follow-up reproduced the missing host artifact or linked a resolving change.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
12
Complexity:
52
Confidence:
70
Actionability:
62
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
12
Complexity:
52
Confidence:
70
Actionability:
62
|
keep 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. | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
12
Complexity:
47
Confidence:
84
Actionability:
65
|
keep open | Snapcraft 3.7.1 --use-lxd completed a build but the .snap appeared only inside LXD, not the host project; a maintainer suspected CWD handling and the discrepancy remains unresolved. | |
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
17
Complexity:
44
Confidence:
82
Actionability:
78
|
needs triage | Snapcraft 3.7.1 built b2 successfully in LXD but left the .snap in the container instead of the host project directory; the report remains untriaged and unconfirmed as fixed. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
8
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. |
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. | |
| #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. | |
| #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. | |
| #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. | |
| #2069292 cannot install system snap "snapd" | snapcraft (launchpad) | closed | Snapcraft build fails injecting host snapcraft into LXC instance ("cannot install system snap snapd"); root cause is host networking — Docker breaks LXD bridge — not a Snapcraft bug. Maintainer pointed to LXD/Docker firewall docs; reporter has not confirmed fix. | |
| #4443 snapcraft on ARM 64 - stuck at lxd | snapcraft | closed | The ARM64 hang was traced to missing LXD container networking, not a Snapcraft architecture defect; Snapcraft 7.5.4 added a timeout instead of looping indefinitely. | |
| #1825820 Snapcraft doesn't update the `snapcraft-project` disk source when the path is moved | snapcraft (launchpad) | open | 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. | |
| #719 Snapcraft fails initialization of build container | craft-providers | closed | LXD startup race was fixed by waiting for instance readiness in craft-providers PR #720; the fix shipped via Snapcraft PR #5247 in Snapcraft 8.6.2. | |
| #1912 lxd: unset SNAP to work-around LXD deb thinking it's a snap | snapcraft | closed | The SNAP-unset workaround for LP #1746612 was rejected and PR #1912 was closed unmerged; no Snapcraft fix landed. | |
| #1892551 snapcraft fails to run if it is installed as a try snap | snapcraft (launchpad) | open | Snapcraft 4.1.5 failed in LXD builds when launched via snap try because snapd cannot export a try-snap file; the affected legacy provider is absent from the current codebase. |