← Back to issue list

snapcraft try with multipass provider crashes

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1996511
Type
issue
State
closed
Author
~peter-sabaini
Labels
—
Created
Updated
Closed

Current evaluation

Snapcraft try with Multipass and core22 was fixed by snapcore/snapcraft#3981 (commit 2691262b8) and shipped in Snapcraft 7.3.

Resolution: closed resolved

Reason: PR snapcore/snapcraft#3981, commit 2691262b8, added core22 support and was merged. A maintainer confirmed the fix was available on edge and released in Snapcraft 7.3.

Evaluated by: mr-cal-bot

No scores available.

Issue body

$ snapcraft try --provider multipass Launching a VM. Build environment is in unknown state, cleaning first. Name: snapcraft-foo State: Running IPv4: 10.160.77.101 Release: Ubuntu 22.04 LTS Image hash: 19f66c4e9576 (Ubuntu Snapcraft builder for Core 22) Load: 0.00 0.03 0.00 Disk usage: 949.6M out of 247.9G Memory usage: 99.6M out of 1.9G Mounts: -- Launched: snapcraft-foo Sorry, an error occurred in Snapcraft: 'core22' We would appreciate it if you anonymously reported this issue. No other data than the traceback and the version of snapcraft in use will be sent. I've agreed to have diagnostics sent, but thought I'd file an issue here as well in case there's questions or more data I can provide. From the traceback it seems that `try` is using the legacy python package, and this only has bionic and focal bases defined: ... File "/snap/snapcraft/8528/lib/python3.8/site-packages/snapcraft_legacy/internal/build_providers/_base_provider.py", line 438, in _setup_environment release=self._get_code_name_from_build_base(), File "/snap/snapcraft/8528/lib/python3.8/site-packages/snapcraft_legacy/internal/build_providers/_base_provider.py", line 369, in _get_code_name_from_build_base return {"core18": "bionic", "core20": "focal"}[build_base] KeyError: 'core22' Version: snapcraft 7.2.7

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Snapcraft try with Multipass and core22 was fixed by snapcore/snapcraft#3981 (commit 2691262b8) and shipped in Snapcraft 7.3.
qwen/qwen3.8-27b — closed resolved snapcraft try crashed with KeyError 'core22' on the multipass provider because the legacy build provider only mapped core18/core20. Fixed by PR #3981 (commit 2691262b8) adding core22 support, released in snapcraft 7.3.
stealth/space-bunny-alpha — closed superseded The core22 Multipass crash was closed without a documented fix. Later craft-providers integration superseded the legacy provider path containing the incomplete base mapping.
qwen/qwen3.6-35b-a3b — — Closed. The multipass provider crashed due to missing core22 base mappings in snapcraft's legacy code. The issue was likely superseded by newer snapcraft releases that updated build provider support.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The multipass provider crashed on core22 due to missing base mappings in the legacy codebase. Superseded by newer snapcraft releases that added core22 support.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The multipass provider crashed due to missing core22 base mappings in the legacy codebase. Lacked activity and comments, indicating abandonment or supersession by updated Snapcraft versions.
qwen3.6-35b-a3b-mtp-q6 — — Closed without comments. The crash resulted from missing core22 mappings in the legacy multipass provider. Likely superseded or resolved in a later release after upstream updated the provider.

Update history

Date Change
created

Related work

Related issues

Issue Project State Summary Similarity
#1947914 concurrent snapcraft builds with multipass provider snapcraft (launchpad) open Snapcraft 5/Core 18 Multipass builds reportedly shared 10.30.202.6 and terminated silently; the old report has no maintainer assessment and needs triage against current versions.
77%
#1806083 snapcraft fails to locate multipass (inside a multipass session) snapcraft (launchpad) open Snapcraft 3.0.1 falsely reported Multipass missing inside a Multipass guest; Darwin-only detection in e9ae8d29f addressed the old path, but the Launchpad record remains open.
74%
#5145 snapcraft fails to launch multipass instance when multipass isn't pre-installed snapcraft open Snapcraft emits cryptic 'Remote "snapcraft" is unknown or unreachable / exit code 2' when Multipass can't launch the build instance; maintainer traced it to image-server unavailability or non-amd64 hosts, fix tracked in craft-providers#211
74%
#1978844 snapcraft try not available for core22-based snap snapcraft (launchpad) closed Core22 support for snapcraft try was merged in canonical/snapcraft#3981 (commit 2691262b8) and released on the edge channel.
73%
#1792614 use multipass if set in the environment snapcraft (launchpad) closed Closed as fixed: PR snapcore/snapcraft#2275 (commit 04f8896d9) made SNAPCRAFT_BUILD_ENVIRONMENT/multipass take precedence over the base-derived provider choice.
73%
#1975468 Snapcraft build fails, because multipass cannot download cloudimg snapcraft (launchpad) closed Snapcraft core20 builds were disrupted by Multipass cloud-image download failures; Launchpad closed the report without documenting a fix, resolving PR, commit, or follow-up.
72%
#2258 build providers: snapcraft images for multipass snapcraft merged Merged PR #2258 as commit 5ffefbf96, adding Snapcraft build images for Multipass and a Darwin launch workaround for LP #1791821.
72%
#1794361 use new multipass snapcraft remote snapcraft (launchpad) closed Snapcraft switched Multipass builds to the new snapcraft: remote via merged PR snapcore/snapcraft#2293 (commit 66060e839).
72%
#2008003 Multipass build provider does not support resource settings core core22 snaps snapcraft (launchpad) open Multipass builds of core22+ snaps ignore SNAPCRAFT_BUILD_ENVIRONMENT_CPU/MEMORY; provider hardcodes 2 CPUs/2GB RAM. Maintainer confirmed unsupported; fix tracked upstream in craft-providers#531.
72%
#4106 Error 2 on snapcraft on linux with multipass: snapcraft closed Multipass's Snapcraft image remote recovered; CI and the reporter succeeded again, and the reporter closed the report as solved without a Snapcraft code change.
72%