snapcraft-managed lxd containers do not respect parallel installs
Metadata
Current evaluation
LXD containers ignored parallel install instance keys, causing build failures. Fixed and resolved via merged pull requests #5085 and #5087.
Suggested action: —
No scores available.
Issue body
In the case when multiple instances of snapcraft are installed in parallel (https://snapcraft.io/docs/parallel-installs) instances suffixed with an instance key (e.g. _foo) appear to install the unsuffixed instance from the host into their managed lxd container. This then results in build failure.
Steps to reproduce:
1) enable parallel installs as described here: https://snapcraft.io/docs/parallel-installs
2) run `snap install snapcraft --channel=6.x/stable --classic` (revision 7201 at reporting time)
3) run `snap install snapcraft_7 --channel=7.x/stable --classic` (revision 8093 at reporting time)
4) initialize a fresh snap using `snapcraft init` and change the base to core22
5) try to run `snapcraft_7` to build that snap
$ snapcraft_7
Launching instance...
Usage: snapcraft pack [OPTIONS] DIRECTORY
Try 'snapcraft pack -h' for help.
Error: No such option: --build-for
Failed to execute pack in instance.
Full execution log: '/home/alex/.cache/snapcraft/log/snapcraft-20220811-135653.968445.log'
Execution log attached to bug report
Lines of interest: 63, 66
I have not tested this using other permutations of versions across parallel installs, or using multipass
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | LXD containers ignored parallel install instance keys, causing build failures. Fixed and resolved via merged pull requests #5085 and #5087. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
60
Quick Win:
36.0
Staleness:
85
Complexity:
40
Confidence:
90
Support Request:
10
|
close not a bug | snapcraft-managed LXD containers do not respect parallel installs, causing build failures when using suffixed parallel installations | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
85
Support Request:
5
|
close stale | Bug where snapcraft-managed LXD containers ignore parallel install instance keys, causing host instance installation and build failures. Inactive for over four years with zero maintainer engagement. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
65
Confidence:
85
Support Request:
5
|
close stale | Bug report detailing that snapcraft-managed LXD containers incorrectly use the unsuffixed host snapcraft instance instead of the parallel-installed suffixed version, causing build failures. Unlabeled and inactive for ~4 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
65
Confidence:
90
Support Request:
5
|
close stale | Bug where snapcraft LXD containers incorrectly use the host's unsuffixed snapcraft instance instead of the parallel-installed suffixed version, causing build failures. Unaddressed for nearly 4 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
65
Confidence:
85
Support Request:
5
|
close stale | Bug report from 2022 describing how snapcraft's LXD containers incorrectly use the host's unsuffixed snapcraft binary instead of the parallel-installed instance, causing build failures. No maintainer response or activity for nearly 4 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4927 Parallel installation of snapcraft not passed to LXD instance | snapcraft | closed | Parallel snapcraft installations were not passed to LXD instances, causing version mismatches. Resolved via pull requests #5085 and #5087, addressing upstream craft-application bug #411. |