I'm running an issue where snapcraft fails with the following output: ----------------------- + snapcraft --debug Launching a VM. Installing build dependencies: libnuma-dev libnuma1 librados-dev librados2 librbd-dev librbd1 libvirt-dev libvirt0 python-pkg-resources python-setuptools python3-pkg-resourc es python3-setuptools E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? Could not install all requested build packages: libnuma-dev libnuma1 librados-dev librados2 librbd-dev librbd1 libvirt-dev libvirt0 python-pkg-resources python-setuptools py thon3-pkg-resources python3-setuptools ----------------------- It looks like the multipass vm is busy running some automated apt tasks in the background, which means that the snapcraft script can't get a lock when installing packages. Everything works if I run snapcraft again from within the vm, though the error message is annoying to come back to after getting up to get a coffee, expecting the snap to loyally build itself while I am away. :-) This happens when building microstack, usually when I'm re-running a build after making changes (I don't think that I've seen this with a fresh build). My snapcraft yaml can be here: https://opendev.org/x/microstack/src/branch/master/snapcraft.yaml Note that I'm adding a ppa and running apt update as part of the build of the uca-sources part, so this may be a self inflicted wound. I'll experiment with ordering, but would appreciate advice on best practices for handling this situation, if my ppa shenanigans are at fault here ...