Doing a test image build with ubuntu-image, and create_chroot and install_packages steps are slower than they could be, because it's running dpkg without libeatmydata.
root 1482906 0.4 0.0 21908 14208 pts/19 S+ 16:27 0:00 | | \_ apt install --assume-yes --quiet --option=Dpkg::options::=--force-unsafe-io --option=Dpkg::Options::=--force-confold apport bcache-tools btrfs-progs byobu cloud-guest-utils cloud-initramfs-copymods cloud-initramfs-dyn-netconf curl dirmngr ethtool fonts-ubuntu-console git gnupg htop lvm2 mdadm motd-news-config multipath-tools overlayroot patch pollinate screen software-properties-common sosreport tmux ubuntu-server update-notifier-common vim xfsprogs adduser apt apt-utils console-setup debconf-i18n dhcpcd-base eject init iproute2 iputils-ping kbd kmod less locales lsb-release netbase netcat-openbsd netplan.io python3 sudo tzdata ubuntu-advantage-tools ubuntu-keyring ubuntu-minimal udev vim-tiny whiptail bind9-dnsutils busybox-static cpio cron dmidecode dosfstools ed file ftp hdparm info lshw lsof man-db nftables parted pciutils psmisc rsync strace time ubuntu-standard usbutils wget xz-utils cloud-init openssh-server ubuntu-server linux-image-generic
$ sudo lsof -p 1482906|grep -i libeatmy
$
Image builds should always run under libeatmydata. dpkg's sync-heavy unpacking process is essential for running systems, but when building images it's just overhead.
