Build Failure: Virtual Memory Exhausted During MySQL Compilation in Nextcloud Snap about nextcloud-snap HOT 6 CLOSED

Yeah, Snapcraft was required to use Multipass as the default backend for political reasons (a straight ask from Mark, hoping that it would make Multipass more popular). It works for simple cases, but anything more complex and it really gets in the way. The Snapcraft devs have maintained the LXD backend as a first-class citizen knowing that a significant number of people would use it instead. Just export SNAPCRAFT_BUILD_ENVIRONMENT=lxd in your ~/.bashrc and move on with your life.

from nextcloud-snap.

I guess you should have some swap partition/file if you are gonna do this with 8GB or RAM.

from nextcloud-snap.

@pachulo is right, you need a sort of ridiculous amount of RAM to build MySQL. I'm not actually sure how much the GitHub runners give us, to be honest, but we haven't had an issue there. Definitely had problems in this area in the past, though.

from nextcloud-snap.

Ok, but I have a machine with physically 32GB of RAM (not fully used during compilation) and the issue persists. The problem is that snapcraft always creates the VM with only 2GB of RAM and I have not found a solution how to avoid that (by using configuration from this repository).

from nextcloud-snap.

That sounds like a snapcraft bug. I personally use the lxd backend instead of multipass, which doesn't have those kinds of limitations. I'm not really sure what knobs snapcraft exposes these days to make that VM usable.

from nextcloud-snap.

That sounds like a snapcraft bug. I personally use the lxd backend instead of multipass, which doesn't have those kinds of limitations. I'm not really sure what knobs snapcraft exposes these days to make that VM usable.

Perfect! Thanks for the suggestion. The use of snapcraft --use-lxd solves the issue. Unfortunately the multipass is used by default for snapcraft without parameters.

from nextcloud-snap.