concurrent snapcraft builds with multipass provider
Metadata
Current evaluation
Concurrent snapcraft builds with the multipass provider assign all instances the same IPv4, aborting builds with no debug info. No labels, comments, or maintainer activity in ~4.8 years; targets snapcraft 5.0 on EOL Ubuntu 18.04/20.04.
Suggested action: close stale
Reason: The issue has had zero maintainer interaction for 1776 days and targets snapcraft 5.0 on Ubuntu 18.04/20.04, both long out of support. The multipass provider has since been substantially reworked (e.g. merged PR snapcraft#2293), and the duplicate-IPv4 symptom is a multipass network-manager behavior rather than snapcraft logic, so the report is no longer actionable against current versions.
Impact:
30
Quick Win:
13.5
Staleness:
95
Complexity:
55
Confidence:
60
Support Request:
10
Issue body
When I try to build multiple snaps concurrently using the multipass provider, all the instances are assigned the same IPv4 address and hence all the builds are abruptly stopped without giving any useful information to debug. The output for the multipass list command looks like this:
Name State IPv4 Image
snapcraft-my-snap Running 10.30.202.6 Ubuntu Snapcraft builder for Core 18
snapcraft-testing Running 10.30.202.6 Ubuntu Snapcraft builder for Core 18
This behavior is unexpected and limits the capability of snapcraft for parallel builds on powerful machines. The issue is observed on both Ubuntu 18.04 and Ubuntu 20.04, with the snapcraft version 5.0 and multipass version 1.7.1.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
13.5
Staleness:
95
Complexity:
55
Confidence:
60
Support Request:
10
|
close stale | Concurrent snapcraft builds with the multipass provider assign all instances the same IPv4, aborting builds with no debug info. No labels, comments, or maintainer activity in ~4.8 years; targets snapcraft 5.0 on EOL Ubuntu 18.04/20.04. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Duplicate IPv4 addresses assigned to concurrent multipass instances during snapcraft builds, causing failures. Untriaged, inactive for over 4 years, and references obsolete software versions. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
10
|
close stale | Concurrent snapcraft builds using the multipass provider assign duplicate IPv4 addresses to instances, causing build failures. Unlabelled, no maintainer interaction, inactive for ~4.7 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
60
Confidence:
85
Support Request:
10
|
close stale | Concurrent snapcraft builds using multipass assign duplicate IPv4 addresses to instances, causing failures. Issue is 4.7 years old, unlabelled, and has no maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Concurrent snapcraft builds using the multipass provider fail due to duplicate IPv4 addresses assigned to build instances. Reported on outdated versions with no maintainer interaction or follow-up. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft#2293
(confidence 45%)
Merged rework of the multipass build provider (new snapcraft: remote) that replaced the provider code paths from the snapcraft 5.0 era this issue targets; not a direct fix for the IP symptom.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1806083 snapcraft fails to locate multipass (inside a multipass session) | snapcraft (launchpad) | open | snapcraft 3.0.1 fails to detect an installed multipass when run inside a multipass VM, prompting to install and dropping the user into a shell. No maintainer activity for ~7 years; affected version is long obsolete. | |
| #1794955 snapcraft erroneously errors when deleting non-existent multipass container | snapcraft (launchpad) | open | snapcraft clean fails with 'instance does not exist' when the multipass container is already gone; reporter suggests treating it as a no-op. Open since 2018, unlabeled, no maintainer activity for ~7.9 years. | |
| #1807125 After snapcraft refresh, old multipass containers no longer work | snapcraft (launchpad) | open | snapcraft reuses outdated multipass containers after snap refresh, causing 'Could not find snap/snapcraft.yaml' errors until snapcraft clean is run; untriaged, no maintainer activity for ~7.7 years | |
| #1810915 snapcraft can't tell when multipass is installed but disabled | snapcraft (launchpad) | open | Snapcraft fails to detect a disabled multipass snap, prompting to install it and then erroring out. Reported against multipass 2018.12.1 / ~2019 snapcraft; untriaged, 0 comments, no labels, inactive for ~7.6 years. |