[Touch-packages] [Bug 2038662] Re: systemd-nspawn error: "Failed to mount image file system: Value too large for defined data type"

I confirmed this issue on 22.04 using the reproducer in the original description. I agree that [1] looks like the appropriate upstream bug. In fact, we currently skip a test in Jammy's autopkgtest due to this issue [2]. Unfortunately, the fix doesn't apply to v249.11 without [3], and I'm not sure

[Touch-packages] [Bug 2038662] Re: systemd-nspawn error: "Failed to mount image file system: Value too large for defined data type"

** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Jammy) Status: New => Confirmed ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Low --

[Touch-packages] [Bug 2038662] Re: systemd-nspawn error: "Failed to mount image file system: Value too large for defined data type"

I note that the issue *doesn't* occur with 23.10 (which has systemd 253.5), tested using an lxd VM: $ lxc launch --vm images:ubuntu/23.10/cloud mythic $ lxc shell mythic # apt-get install systemd-container ... # machinectl pull-raw

[Touch-packages] [Bug 2038662] Re: systemd-nspawn error: "Failed to mount image file system: Value too large for defined data type"

Grr... it works if I first run a dummy command within the machine: systemd-nspawn -M jammy-rootfs --as-pid2 passwd root machinectl start jammy-rootfs # it's working now! machinectl login jammy-rootfs (Even just "echo hello world" does the job) However if you go back to a *fresh* image then

[Touch-packages] [Bug 2038662] Re: systemd-nspawn error: "Failed to mount image file system: Value too large for defined data type"

** Description changed: Two-line reproducer: run this on an Ubuntu 22.04 server. sudo machinectl pull-raw http://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img jammy-rootfs sudo machinectl start jammy-rootfs Response: Job for