Comment 2 for bug 1865027

This seems to be happening again :/ Logs attached. In curtin's install.log I see the following:

dpkg: error processing archive /tmp/apt-dpkg-install-643qVf/19-linux-headers-5.4.0-18_5.4.0-18.22_all.deb (--unpack):
 cannot copy extracted data for './usr/src/linux-headers-5.4.0-18/tools/testing/selftests/sparc64/drivers/drivers_test.sh' to '/usr/src/linux-headers-5.4.0-18/tools/testing/selftests/sparc64/drivers/drivers_test.sh.dpkg-new': failed to write (No space left on device)

but if I mount /dev/vda2 it's an almost empty filesystem:

Filesystem Size Used Avail Use% Mounted on
/dev/vda2 7.4G 34M 6.9G 1% /target

According to the kernel log the mount did happen at install time:

Mar 31 14:42:48 ubuntu-server kernel: [ 295.394200] EXT4-fs (vda2): mounted filesystem with ordered data mode. Opts: (null)

Subiquity's snapcraft.yaml currently points to one of the latest curtin commits, and the following commits do not seem related to the failure, at least at first glance. However I'm not sure on the exact version of curtin being used on the arm64 subiquity snap (LP: 865075).