Comment 7 for bug 1991285

Revision history for this message
Nick Rosbrook (enr0n) wrote :

Thanks for reviewing, Steve.

I took a closer look at this. The failure is indeed caused by the container environment, and not something specific to the armhf arch. In particular, the lxd images ship with a non-empty /etc/fstab which contains an entry for a disk label that is not present:

root@autopkgtest-lxd-iameji:/tmp/autopkgtest.DW7ZuH/build.h0Z/src# blkid -o list
device fs_type label mount point UUID
-------------------------------------------------------------------------------------------------------
root@autopkgtest-lxd-iameji:/tmp/autopkgtest.DW7ZuH/build.h0Z/src# cat /etc/fstab
LABEL=cloudimg-rootfs / ext4 defaults 0 1

Hence, systemd-remount-fs.service fails with the errors shown in comment #4. I think it would be better to ignore the failure in containers instead of just armhf.