I've just tried a live-build cross build of an armhf image from an amd64 VM, with debootstrap 1.0.78, and had it fail this way too.
Debian: stretch (last updated five minutes ago) live-build: 1:20151215 (but reports as 5.0~a11-1) debootstrap: 1.0.78 qemu: 1:2.5+dfsg-5 The command to reproduce the error is: lb config \ --apt-indices none \ --apt-source-archives false \ --distribution wheezy \ --binary-images hdd \ --hdd-size 512 \ --architectures armhf \ --bootstrap-qemu-arch armhf \ --bootstrap-qemu-static /usr/bin/qemu-arm-static \ --firmware-binary false \ --firmware-chroot false sudo lb build 2>&1 | tee build_log The final part of the build log says: P: Running debootstrap second stage under QEMU I: Keyring file not available at /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror https://mirrors.kernel.org/debian P: Begin unmounting filesystems... P: Saving caches... /usr/bin/env: apt-get: No such file or directory Full log: https://gist.github.com/detly/52a830858f539682764f Is this a bug? Or am I doing something unsupported? I didn't know enough to know if this was a -live or -boot issue. (Also, sorry for breaking threading, but I wasn't subscribed to -boot.) Cheers, Jason Heeris