vmbuilder does not work for ubuntu 18.04

[achow101]

vmbuilder does not work on ubuntu 18.04 and thus cannot be used to create the kvm base images on ubuntu 18.04. Furthermore, vmbuilder itself has not been substantially updated in several years (latest I could find was 2010). We should migrate away from using vmbuilder or we should package an updated version of vmbuilder and use that.

[achow101]

https://github.com/newroco/vmbuilder is a fork of vmbuilder which seems to work for me. We could package it with gitian-builder (in the same way that Bitcoin Core packages leveldb, univalue, etc. as sub-directories in the git tree) and just use it for building the VMs instead of relying on the outdated version.

[josephbisch]

I had updated the README to point to https://github.com/newroco/vmbuilder, but it looks like I only changed it under the Arch Linux heading, so that Gentoo and Ubuntu still say to use their respective packages.

[maflcko]

I believe it is possible to create the base image on another disto and move it over to bionic or whatever your current os is.

[TTcoinDeveloper]

18.04 takes to long to install in any case slow

[luke-jr]

https://github.com/newroco/vmbuilder does NOT work for me, FWIW.

[ultra-pool]

Fails on ubuntu 14 also

[TTcoinDeveloper]

It will build on 14.04 are you trying to build a 64 bit vm on a 32 bit machine? I have done this on 14.04 before

[pacepace]

I've got it [EDIT: it being the vmbuilder from newroco] working to build Xenial, but it gets hung on umounting when trying to build Bionic. It cannot umount because of this file in the tmp build structure: /%TMP_BUILD_DIR%/tmp/vmbuilder-grub/tmp%RANDOM% (where %TMP_BUILD_DIR% is usually under /tmp and %RANDOM% is a random string of 6 digits).

I cannot remove that file as root and so far have been unable to find what has it open in lsof or fuser. So far I have to reboot to be able to delete. I'm guessing this has to do with a chroot, but I haven't gotten beyond that yet.

For those who wonder, I have the sleep(10) patch in place for both the dev and disk umount, that isn't the issue in this case.