Response:
Job for <email address hidden> failed because the control process exited with error code.
Here's the relevant output from "journalctl -xeu <email address hidden>"
--------
░░ A start job for unit <email address hidden> 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]: <email address hidden>: 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 <email address hidden> has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Oct 06 13:13:21 brian-kit systemd[1]: <email address hidden>: Failed with result 'exit-code'.
--------
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 <email address hidden> failed because the control process exited with error code.
Here's the relevant output from "journalctl -xeu <email address hidden>" nspawn[ 36720]: Failed to mount image file system: Value too large for defined data type nspawn[ 36688]: Short read while reading cgroup mode (0 bytes). The child is most likely dead. www.ubuntu. com/support
--------
░░ A start job for unit <email address hidden> has begun execution.
░░
░░ The job identifier is 3223.
Oct 06 13:13:21 brian-kit systemd-
Oct 06 13:13:21 brian-kit systemd-
Oct 06 13:13:21 brian-kit systemd[1]: <email address hidden>: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://
░░
░░ An ExecStart= process belonging to unit <email address hidden> has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Oct 06 13:13:21 brian-kit systemd[1]: <email address hidden>: 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?
ProblemType: Bug ature: Ubuntu 5.15.0- 84.93-generic 5.15.116 dules: zfs zunicode zavl icp zcommon znvpair esult: pass 256color
DistroRelease: Ubuntu 22.04
Package: systemd-container 249.11-0ubuntu3.10
ProcVersionSign
Uname: Linux 5.15.0-84-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
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-
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)