Hello,
I have a problem with systemd when a secondary disk is added to a container (image: debian/bullseye/cloud on arm64). This problem is present on all my containers with a secondary disk pointing to a folder on my NAS. Do you have any idea?
I reproduce the problem with the following steps:
$ lxc exec infra-rproxy-2223 -- sudo /usr/bin/systemctl is-system-running
starting
$ lxc exec infra-rproxy-2223 -- sudo /usr/bin/systemctl is-system-running
running
$ lxc config device add infra-rproxy-2223 data disk source=/mnt/pumbaa/containers/infra-rproxy-2223.gaia.ykn.local path=/mnt/data
Device data added to infra-rproxy-2223
$ lxc exec infra-rproxy-2223 -- sudo /usr/bin/systemctl is-system-running
running
$ lxc restart infra-rproxy-2223
$ lxc exec infra-rproxy-2223 -- sudo /usr/bin/systemctl is-system-running
degraded
$ lxc exec infra-rproxy-2223 -- df -h /mnt/data
Filesystem Size Used Avail Use% Mounted on
192.168.1.1:/mnt/ronflex/chaos/infra-rproxy-2228.gaia.ykn.local 24T 40G 24T 1% /mnt/data
$ lxc exec infra-rproxy-2223 -- systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-logind.service loaded failed failed User Login Management
[...]
$ lxc exec infra-rproxy-2223 -- systemctl status systemd-logind.service
● systemd-logind.service - User Login Management
Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
Drop-In: /run/systemd/system/service.d
└─zzz-lxc-service.conf
Active: failed (Result: exit-code) since Mon 2022-07-25 17:01:02 UTC; 52s ago
Docs: man:sd-login(3)
man:systemd-logind.service(8)
man:logind.conf(5)
man:org.freedesktop.login1(5)
Process: 364 ExecStart=/lib/systemd/systemd-logind (code=exited, status=226/NAMESPACE)
Main PID: 364 (code=exited, status=226/NAMESPACE)
CPU: 20ms
Jul 25 17:01:02 infra-rproxy-2223 systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE
Jul 25 17:01:02 infra-rproxy-2223 systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
Jul 25 17:01:02 infra-rproxy-2223 systemd[1]: Failed to start User Login Management.
Jul 25 17:01:02 infra-rproxy-2223 systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5.
Jul 25 17:01:02 infra-rproxy-2223 systemd[1]: Stopped User Login Management.
Jul 25 17:01:02 infra-rproxy-2223 systemd[1]: systemd-logind.service: Start request repeated too quickly.
Jul 25 17:01:02 infra-rproxy-2223 systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
Jul 25 17:01:02 infra-rproxy-2223 systemd[1]: Failed to start User Login Management.
$ lxc config device remove infra-rproxy-2223 data
Device data removed from infra-rproxy-2223
$ lxc exec infra-rproxy-2223 -- sudo /usr/bin/systemctl is-system-running
running
Informations:
Host
Hardware: Odroid C4
Architecture: arm64
OS: Armbian 22.05.4 (Debian Bullseye 11.4)
lxd: 5.3-91e042b (snap package)
Guest
type: container
OS: debian/bullseye/cloud