Container names are inconsistent lxd vs multipass
Metadata
Current evaluation
LXD and Multipass now use the same snapcraft-prefixed build instance name; the old mismatch could not be reproduced and appears resolved by the shared provider naming path.
Suggested action: close resolved
Reason: Commit 2980d145c (snapcraft#3943) moved builds to the shared craft-providers interface; current providers.py generates a snapcraft-prefixed name and lifecycle.py passes that same instance_name to either backend. The sole maintainer comment also reported that both environments created a snapcraft-foo instance.
Evaluated by: mr-cal-bot
Impact:
25
Quick Win:
18
Complexity:
12
Confidence:
92
Actionability:
84
Issue body
If I use lxd I get a snapcraft-foo-bar-baz named container.
With newer snapcraft if I use multipass I get a random foo-bar named container.
Can these please be consistent. I often have lots of containers running and it's better for me to be able to spot the snapcraft ones.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
18
Complexity:
12
Confidence:
92
Actionability:
84
|
close resolved | LXD and Multipass now use the same snapcraft-prefixed build instance name; the old mismatch could not be reproduced and appears resolved by the shared provider naming path. | |
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
8
Complexity:
18
Confidence:
82
Actionability:
38
|
close stale | Reported 2019 Multipass/LXD build-environment naming mismatch could not be reproduced; current code uses a shared snapcraft-prefixed name, and the reporter never confirmed whether it was fixed. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
14
Complexity:
20
Confidence:
60
Actionability:
60
|
keep open | Inconsistent container naming between LXD (snapcraft-*) and Multipass (random names). Issue requests consistent naming for easier identification. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
15
Staleness:
95
Complexity:
25
Confidence:
55
Support Request:
30
|
needs triage | Request for consistent build container naming between LXD (snapcraft-<name>) and Multipass (random <name>) so snapcraft containers are easy to spot. No labels, no comments, no maintainer activity for ~7.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Feature request to standardize container naming across LXD and Multipass backends for easier identification. The issue has been inactive for over 7 years with no maintainer labels or responses. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Requests consistent naming for snapcraft-created containers across LXD and Multipass backends. Currently LXD uses predictable prefixes while Multipass generates random names. Unaddressed for over 8 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Request to standardize container naming between LXD and Multipass backends in Snapcraft. Unlabelled, zero comments, and over 8 years old with no maintainer engagement. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcraft#3943
(confidence 82%)
The shared craft-providers refactor replaced the old provider-specific naming behavior with a common instance name.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #226 use multipass compatible instance names | craft-providers | closed | Fixed by merged PR #712, which normalizes Multipass instance names using LXD-compatible hostname validation and truncation. |