multipass build dies - possibly OOM killed
Metadata
Current evaluation
Multipass builds gained configurable RAM and disk sizes in PR #2260 (commit 8d9cc5c5a), resolving the 1 GB VM/OOM limitation.
Resolution: closed resolved
Reason: The linked resolution was snapcore/snapcraft PR #2260, recorded as commit 8d9cc5c5a. It added configurable RAM and disk sizing for build VMs, allowing the default 1 GB Multipass VM to be increased.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Testing a build in multipass with:-
export SNAPCRAFT_BUILD_ENVIRONMENT=multipass
snapcraft cleanbuild
Killed
Failed to run 'override-build': Exit code was 137.
An error occurred when trying to execute "sh -c 'cd che; /snap/bin/snapcraft snap --output che_6.10.0_amd64.snap'" with 'multipass': returned exit code 2.
Here's the (simple) yaml to reproduce it if you're inclined.
----8<----
name: che
version: '6.10.0'
summary: Eclipse CHE
description: |
Next-generation Eclipse IDE. Open source workspace server and cloud IDE.
grade: stable
confinement: strict
parts:
che:
plugin: maven
source: https://github.com/eclipse/che.git
override-build: |
mvn -e -DskipTests=true -Dfindbugs.skip=true -Dgwt.compiler.localWorkers=2 -T 1C -Dmdep.analyze.skip=true -Dlicense.skip=true -Pnative clean install
build-packages:
- golang
----8<----
I didn't get any kind of sentry option nor indication why it failed. I have run it again, and it looks like we have 1GB RAM and 4GB disk set aside for the VM. Is that enough I wonder?
multipass info confarreated-deacon
Name: confarreated-deacon
State: RUNNING
IPv4: 10.161.160.203
Release: Ubuntu 16.04.5 LTS
Image hash: c0d099383cd0 (Ubuntu 16.04 LTS)
Load: 1.64 0.87 0.35
Disk usage: 1.2G out of 4.8G
Memory usage: 132.7M out of 992.1M
Mounts: /var/lib/snapd/snaps => /var/cache/snapcraft/snaps
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Multipass builds gained configurable RAM and disk sizes in PR #2260 (commit 8d9cc5c5a), resolving the 1 GB VM/OOM limitation. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved by merged PR snapcore/snapcraft#2260 (commit 8d9cc5c5a), adding RAM and disk size overrides for Multipass build VMs. | |
| stealth/space-bunny-alpha | — | closed resolved | Multipass builds died with exit 137 (OOM) because the VM had only 1GB RAM/4GB disk and there was no way to change it; fixed by snapcraft#2260 (commit 8d9cc5c5a) adding RAM/disk size overrides for build providers. | |
| stealth/space-bunny-alpha | — | closed stale | Exit 137 was a likely 1 GB VM OOM during Maven. Snapcraft later added configurable Multipass RAM/disk in #2260 (8d9cc5c5a); no fix or closing explanation is recorded here. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The Multipass build failed with exit code 137 due to insufficient 1GB RAM causing an OOM kill. No comments or fixes were provided, indicating the issue was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Closed without resolution or activity. The multipass build failure was attributed to possible OOM kills, but no fix was provided. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2260
(confidence 99%)
The PR added RAM and disk-size configuration for build providers and was cited in the issue's final maintainer comment.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1842376 No standard way of specifying memory requirements for multipass build VMs | snapcraft (launchpad) | open | Open, unlabelled request for a project-level Multipass RAM setting: Go builds are OOM-killed at the documented 2 GiB default, while only an environment-variable override is available. |