Snapcraft

Setting SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY doesn't take effect

Bug #1814729 reported by Alan Pope 🍺🐧🐱 🦄
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Snapcraft
Triaged
Medium
Unassigned

Bug Description

I have a snap which is very large and failed to build due to running out of memory in multipass. I set SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY=8G and re-ran snapcraft. It re-used the previous VM rather than noting the change in RAM, to take the opportunity to launch a new one. Perhaps snapcraft could detect the change in resources and act accordingly, cleaning or at least suggesting a clean is worthwhile if the environment around multipass changes?

Sergio Schvezov (sergiusens)
tags: added: 18.10-build-vm
Changed in snapcraft:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
David Jung (djung) wrote :

Note that it only takes effect when the multipass VM machine is created. Hence, if you have an existing VM, you not only need to use multipass to stop it, you also need to delete it (and purge the deleted image) before snapcraft re-create it and in doing so check the environment variables.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.