snapcraft failed to build with cleanbuild on 18.04
Metadata
Current evaluation
Expired after 60 days without activity; no fix was recorded. A maintainer advised using --destructive-mode because cross-compilation in build environments was unsupported.
Resolution: closed stale
Reason: Launchpad's janitor closed the report on 2019-03-25 after 60 days without activity. No resolving PR or commit was recorded; the earlier maintainer response redirected the reporter to --destructive-mode.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Posted and had some discussions on https://forum.snapcraft.io/t/building-for-core18-multipass-issue/8958
I also encountered the similar the issue when I used snapcraft to create a uc18 gadget for arm64:
$ snapcraft cleanbuild --target-arch=arm64
Setting target machine to 'arm64'
Creating snapcraft-loudly-fresh-mole
Starting snapcraft-loudly-fresh-mole
...
You need multipass installed to build snaps which use the base keyword.
Would you like to install it now? [y/N]: y
snapd is not logged in, snap install commands will use sudo
multipass (beta) 2018.12.1 from Canonical✓ installed
Channel latest/beta for multipass is closed; temporarily forwarding to beta.
Waiting for multipass...
Setting target machine to 'arm64'
Launching a VM.
launch failed: modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.15.0-1030-oem/modules.dep.bin'
modprobe: FATAL: Module msr not found in directory /lib/modules/4.15.0-1030-oem
An error occurred when trying to launch the instance with 'multipass': returned exit code 2.
Ensure that 'multipass' is setup correctly and try again.
Error: not found
Stopping local:snapcraft-loudly-fresh-mole
An error occurred when trying to copy files using 'lxd': returned exit code 1
I tried to install mulitpass snap on native system, and it did work with launch. However, I'm not sure why reported "msr module missing" during snapcraft.
There are some information provided:
$ snapcraft --version
snapcraft, version 2.43.1+18.4
$ snap --version
snap 2.36.3
snapd 2.36.3
series 16
ubuntu 18.04
kernel 4.15.0-1030-oem
$ lsmod | grep msr
msr 16384 0
$ snap list
Name Version Rev Tracking Publisher Notes
core 16-2.36.3 6130 stable canonical✓ core
gnome-3-26-1604 3.26.0 74 stable/… canonical✓ -
gnome-calculator 3.30.1 260 stable/… canonical✓ -
gnome-characters 3.30.0 139 stable/… canonical✓ -
gnome-logs 3.30.0 45 stable/… canonical✓ -
gnome-system-monitor 3.30.0 57 stable/… canonical✓ -
gtk-common-themes 0.1-4-g88bc1b2 818 stable/… canonical✓ -
hw-probe 1.4-10 153 stable linuxhw -
multipass 2018.12.1 572 beta canonical✓ classic
ubuntu-image 1.4+snap3 104 stable canonical✓ classic
$ multipass launch
Launched: full-ribbonfish
$ multipass list
Name State IPv4 Release
full-ribbonfish RUNNING 10.127.219.211 Ubuntu 18.04 LTS
$ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
If "cleanbuild" option relies on multipass or lxd, how to deal with this case?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Expired after 60 days without activity; no fix was recorded. A maintainer advised using --destructive-mode because cross-compilation in build environments was unsupported. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as expired after 60 days without activity; no fix was recorded. The reporter was advised to use --destructive-mode because cross-compilation in build environments was unsupported. | |
| stealth/space-bunny-alpha | — | closed stale | No fix or maintainer response was recorded for the Ubuntu 18.04 Multipass/cleanbuild failure; the report was closed without a documented resolution. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The multipass cleanbuild failure caused by a missing msr module was likely abandoned or superseded by newer snapcraft and multipass releases that resolved the underlying compatibility issues. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The report details a multipass cleanbuild failure on Ubuntu 18.04 due to a missing msr module error. No fix was implemented, and the discussion was redirected to the Snapcraft forum. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The snapcraft cleanbuild failure on Ubuntu 18.04 caused by multipass VM launch errors was abandoned or superseded by updated build tooling and multipass versions. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution or comments. The reported multipass cleanbuild failure due to a missing msr module on Ubuntu 18.04 was likely abandoned or superseded by newer snapcraft and multipass versions. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1697979 snapcraft fails on initial cleanbuild probe | snapcraft (launchpad) | closed | Closed as obsolete: cleanbuild was decommissioned, and standard Snapcraft builds now transparently use a clean build environment. | |
| #1800119 snapcraft cleanbuild | snapcraft (launchpad) | closed | The obsolete cleanbuild command was retired because builds became clean by default; a maintainer closed the report in August 2023. | |
| #1788654 snapcraft cleanbuild doesn't work with cross-compile stage-packages | snapcraft (launchpad) | closed | Closed as an obsolete legacy cleanbuild/LXD issue after a maintainer directed users to migrate to bases; no targeted cross-architecture fix was recorded. | |
| #2044389 snapcraft clean failed but exit 0 | snapcraft (launchpad) | open | Snapcraft 7.5.3 reports a missing build environment during clean but exits 0; a maintainer confirmed the bug and agreed it should fail, with no fix recorded. | |
| #1816042 snapcraft cleanbuild fails if container isn't fully ready | snapcraft (launchpad) | closed | Closed as obsolete: @sergiusens said cleanbuild was no longer supported because normal builds now transparently provide clean builds. | |
| #1746359 snapcraft cleanbuild --debug should provide guidance on build failure | snapcraft (launchpad) | closed | Superseded by Snapcraft 3.x base-based build environments, which replaced the legacy cleanbuild --debug container workflow. | |
| #1746381 snapcraft cleanbuild shouldn't always delete container at end | snapcraft (launchpad) | closed | No fix was made: maintainers confirmed cleanbuild containers were disposable, recommended SNAPCRAFT_CONTAINER_BUILDS, and left the request for default failure shells unimplemented. | |
| #1866300 snapcraft fails to build core20 snap | snapcraft (launchpad) | closed | Closed without a documented fix after core20 Multipass/LXD failures; core20 build-base support was unavailable and the workaround was destructive mode. | |
| #1609803 snapcraft cleanbuild --no-clean-up | snapcraft (launchpad) | closed | Cleanbuild debugging landed in snapcore/snapcraft PR #740 (commit a24083e75); follow-up PR #1404 made --debug enter a shell when builds fail. | |
| #1988858 snapcraft trying to install extra package causing conflict | snapcraft (launchpad) | closed | Expired and closed without a fix after 60 days of inactivity; maintainers could not reproduce the conflict and suspected a transient archive state. |