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

[Nick Rosbrook]

** 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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2038662

Title:
  systemd-nspawn error: "Failed to mount image file system: Value too
  large for defined data type"

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  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 systemd-nspawn at jammy-rootfs.service failed because the control process exited with error code.

  Here's the relevant output from "journalctl -xeu systemd-nspawn at jammy-rootfs.service"
  --------
  ░░ A start job for unit systemd-nspawn at jammy-rootfs.service has begun execution.
  ░░
  ░░ The job identifier is 3223.
  Oct 06 13:13:21 brian-kit systemd-nspawn[36720]: Failed to mount image file system: Value too large for defined data type
  Oct 06 13:13:21 brian-kit systemd-nspawn[36688]: Short read while reading cgroup mode (0 bytes). The child is most likely dead.
  Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn at jammy-rootfs.service: Main process exited, code=exited, status=1/FAILURE
  ░░ Subject: Unit process exited
  ░░ Defined-By: systemd
  ░░ Support: http://www.ubuntu.com/support
  ░░
  ░░ An ExecStart= process belonging to unit systemd-nspawn at jammy-rootfs.service has exited.
  ░░
  ░░ The process' exit code is 'exited' and its exit status is 1.
  Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn at jammy-rootfs.service: Failed with result 'exit-code'.
  --------

  This appears to be similar to
  https://github.com/systemd/systemd/issues/20989

  If so, a fix was committed in March 2022: https://github.com/systemd/systemd/pull/22774
  but maybe that was too late for 22.04? Or this is a different problem?

  EDIT: the reproducer from
  https://github.com/systemd/systemd/issues/20989#issuecomment-997024152
  also reproduces the problem.

  # rm -rf /var/lib/machines/my-container/
  # mkdir -p /var/lib/machines/my-container/etc
  # cp /etc/os-release /var/lib/machines/my-container/etc/
  # systemd-nspawn -U -b -D /var/lib/machines/my-container/
  Spawning container my-container on /var/lib/machines/my-container.
  Press ^] three times within 1s to kill container.
  Selected user namespace base 972619776 and range 65536.
  Failed to create directory at /var/lib/machines/my-container/usr: Value too large for defined data type

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd-container 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  Uname: Linux 5.15.0-84-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Fri Oct  6 13:10:41 2023
  InstallationDate: Installed on 2022-11-04 (335 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038662/+subscriptions