Package: vmdebootstrap Version: 1.5-1 Severity: important When --enable-dhcp is used and systemd-network is used, systemd-resolved is not started. In addition, I think even if you start systemd-resolved, you still need to point resolv.conf at 127.0.0.53. Installing resolvconf and enabling systemd-resolved seems to be sufficient.
In the current state, debootstrap copies the resolv.conf from the build system into the machine leaving it there. This is often a very bad choice for the resulting image. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (550, 'testing'), (500, 'stable-updates'), (500, 'stable'), (200, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vmdebootstrap depends on: ii debootstrap 1.0.81 ii extlinux 3:6.03+dfsg-14 ii kpartx 0.6.1-3 ii libjs-sphinxdoc 1.4.4-2 ii mbr 1.1.11-5+b1 ii parted 3.2-15 ii python-cliapp 1.20160316-1 ii python-distro-info 0.14 ii python2.7 2.7.12~rc1-2 pn python:any <none> ii qemu-utils 1:2.6+dfsg-3 Versions of packages vmdebootstrap recommends: ii grub2-common 2.02~beta2-36 ii python-guestfs 1:1.32.4-2 ii qemu-system 1:2.6+dfsg-3 ii qemu-user-static 1:2.6+dfsg-3 ii squashfs-tools 1:4.3-3 Versions of packages vmdebootstrap suggests: pn cmdtest <none> pn pandoc <none> pn u-boot:armhf <none> -- no debconf information
