URGENT - Failed Upgrade - 24.04 - No network (LXC)

S

ShaunG

Member
Jul 12, 2022
37
3
11
Hi,

I've just upgraded 7 LXC containers to 24.04 from 22.04, 6 of the upgrades are completely fine but one of them refuses to boot.

Starting the container in foreground, logs below:

Bash: 
Read-only bind remount failed, ignoring: Permission denied
Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Queued start job for default target graphical.target.
[  OK  ] Created slice system-container\x2dgetty.slice - Slice /system/container-getty.
[  OK  ] Created slice system-modprobe.slice - Slice /system/modprobe.
[  OK  ] Created slice system-postfix.slice - Slice /system/postfix.
[  OK  ] Created slice user.slice - User and Session Slice.
[  OK  ] Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target integritysetup.target - Local Integrity Protected Volumes.
[  OK  ] Reached target nss-user-lookup.target - User and Group Name Lookups.
[  OK  ] Reached target slices.target - Slice Units.
[  OK  ] Reached target swap.target - Swaps.
[  OK  ] Reached target veritysetup.target - Local Verity Protected Volumes.
[  OK  ] Listening on rpcbind.socket - RPCbind Server Activation Socket.
[  OK  ] Listening on syslog.socket - Syslog Socket.
[  OK  ] Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
[  OK  ] Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
[  OK  ] Listening on systemd-journald.socket - Journal Socket.
[  OK  ] Listening on systemd-networkd.socket - Network Service Netlink Socket.
         Mounting dev-hugepages.mount - Huge Pages File System...
         Starting systemd-journald.service - Journal Service...
         Starting keyboard-setup.service - Set the console keyboard layout...
         Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
         Starting systemd-sysctl.service - Apply Kernel Variables...
         Starting systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully...
[  OK  ] Mounted dev-hugepages.mount - Huge Pages File System.
systemd-sysctl.service: Failed to set up credentials: Protocol error
systemd-sysctl.service: Main process exited, code=exited, status=243/CREDENTIALS
systemd-sysctl.service: Failed with result 'exit-code'.
[FAILED] Failed to start systemd-sysctl.service - Apply Kernel Variables.
See 'systemctl status systemd-sysctl.service' for details.
[  OK  ] Finished systemd-remount-fs.service - Remount Root and Kernel File Systems.
systemd-tmpfiles-setup-dev-early.service: Failed to set up credentials: Protocol error
systemd-tmpfiles-setup-dev-early.service: Main process exited, code=exited, status=243/CREDENTIALS
systemd-tmpfiles-setup-dev-early.service: Failed with result 'exit-code'.
[FAILED] Failed to start systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully.
See 'systemctl status systemd-tmpfiles-setup-dev-early.service' for details.
         Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev...
systemd-tmpfiles-setup-dev.service: Failed to set up credentials: Protocol error
systemd-tmpfiles-setup-dev.service: Main process exited, code=exited, status=243/CREDENTIALS
systemd-tmpfiles-setup-dev.service: Failed with result 'exit-code'.
[FAILED] Failed to start systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
See 'systemctl status systemd-tmpfiles-setup-dev.service' for details.
[  OK  ] Finished keyboard-setup.service - Set the console keyboard layout.
[  OK  ] Reached target local-fs-pre.target - Preparation for Local File Systems.
[  OK  ] Reached target local-fs.target - Local File Systems.
[  OK  ] Listening on systemd-sysext.socket - System Extension Image Management (Varlink).
         Starting apparmor.service - Load AppArmor profiles...
         Starting console-setup.service - Set console font and keymap...
         Starting plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target cryptsetup.target - Local Encrypted Volumes.
[  OK  ] Reached target paths.target - Path Units.
         Starting ufw.service - Uncomplicated firewall...
[  OK  ] Started systemd-journald.service - Journal Service.
         Starting systemd-journal-flush.service - Flush Journal to Persistent Storage...
[  OK  ] Finished console-setup.service - Set console font and keymap.
[  OK  ] Finished ufw.service - Uncomplicated firewall.
[  OK  ] Reached target network-pre.target - Preparation for Network.
         Starting systemd-networkd.service - Network Configuration...
[  OK  ] Finished plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data.
[FAILED] Failed to start systemd-networkd.service - Network Configuration.
See 'systemctl status systemd-networkd.service' for details.
         Starting systemd-networkd.service - Network Configuration...
[FAILED] Failed to start systemd-networkd.service - Network Configuration.
See 'systemctl status systemd-networkd.service' for details.
         Starting systemd-networkd.service - Network Configuration...
[FAILED] Failed to start systemd-networkd.service - Network Configuration.
See 'systemctl status systemd-networkd.service' for details.
         Starting systemd-networkd.service - Network Configuration...
[FAILED] Failed to start systemd-networkd.service - Network Configuration.
See 'systemctl status systemd-networkd.service' for details.
         Starting systemd-networkd.service - Network Configuration...
[FAILED] Failed to start systemd-networkd.service - Network Configuration.
See 'systemctl status systemd-networkd.service' for details.
[FAILED] Failed to start systemd-networkd.service - Network Configuration.
See 'systemctl status systemd-networkd.service' for details.
[  OK  ] Finished systemd-journal-flush.service - Flush Journal to Persistent Storage.
         Starting systemd-tmpfiles-setup.service - Create Volatile Files and Directories...
[FAILED] Failed to start systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
         Mounting run-rpc_pipefs.mount - RPC Pipe File System...
         Starting rpcbind.service - RPC bind portmap service...
         Starting systemd-resolved.service - Network Name Resolution...
[  OK  ] Reached target time-set.target - System Time Set.
         Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
[  OK  ] Mounted run-rpc_pipefs.mount - RPC Pipe File System.
[  OK  ] Reached target rpc_pipefs.target.
[  OK  ] Reached target nfs-client.target - NFS client services.
[  OK  ] Started rpcbind.service - RPC bind portmap service.
[  OK  ] Reached target remote-fs-pre.target - Preparation for Remote File Systems.
[  OK  ] Reached target rpcbind.target - RPC Port Mapper.
[FAILED] Failed to start systemd-resolved.service - Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
         Starting systemd-resolved.service - Network Name Resolution...
[  OK  ] Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
[FAILED] Failed to start systemd-resolved.service - Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
         Starting systemd-resolved.service - Network Name Resolution...
[FAILED] Failed to start systemd-resolved.service - Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
         Starting systemd-resolved.service - Network Name Resolution...
[FAILED] Failed to start systemd-resolved.service - Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
         Starting systemd-resolved.service - Network Name Resolution...
[FAILED] Failed to start systemd-resolved.service - Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[FAILED] Failed to start systemd-resolved.service - Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Reached target network.target - Network.
[  OK  ] Reached target network-online.target - Network is Online.
[  OK  ] Reached target nss-lookup.target - Host and Network Name Lookups.
         Mounting mnt-nextcloud.mount - /mnt/nextcloud...
         Starting rpc-statd-notify.service - Notify NFS peers of a restart...
[FAILED] Failed to mount mnt-nextcloud.mount - /mnt/nextcloud.
See 'systemctl status mnt-nextcloud.mount' for details.
[DEPEND] Dependency failed for remote-fs.target - Remote File Systems.
[  OK  ] Started rpc-statd-notify.service - Notify NFS peers of a restart.
[FAILED] Failed to start apparmor.service - Load AppArmor profiles.
See 'systemctl status apparmor.service' for details.
[  OK  ] Reached target sysinit.target - System Initialization.
[  OK  ] Started apt-daily.timer - Daily apt download activities.
[  OK  ] Started apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
[  OK  ] Started dpkg-db-backup.timer - Daily dpkg database backup timer.
[  OK  ] Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
[  OK  ] Started logrotate.timer - Daily rotation of log files.
[  OK  ] Started man-db.timer - Daily man-db regeneration.
[  OK  ] Started motd-news.timer - Message of the Day.
[  OK  ] Started phpsessionclean.timer - Clean PHP session files every 30 mins.
[  OK  ] Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
[  OK  ] Reached target timers.target - Timer Units.
[  OK  ] Listening on dbus.socket - D-Bus System Message Bus Socket.
[  OK  ] Listening on ssh.socket - OpenBSD Secure Shell server socket.
[  OK  ] Listening on uuidd.socket - UUID daemon activation socket.
[  OK  ] Reached target sockets.target - Socket Units.
[  OK  ] Reached target basic.target - Basic System.
         Starting accounts-daemon.service - Accounts Service...
         Starting apache2.service - The Apache HTTP Server...
[  OK  ] Started cron.service - Regular background program processing daemon.
         Starting dbus.service - D-Bus System Message Bus...
[  OK  ] Started dmesg.service - Save initial kernel messages after boot.
         Starting networkd-dispatcher.service - Dispatcher daemon for systemd-networkd...
         Starting nginx.service - LSB: starts the nginx web server...
         Starting postfix@-.service - Postfix Mail Transport Agent (instance -)...
         Starting redis-server.service - Advanced key-value store...
         Starting rsyslog.service - System Logging Service...
         Starting systemd-logind.service - User Login Management...
         Starting systemd-user-sessions.service - Permit User Sessions...
[FAILED] Failed to start accounts-daemon.service - Accounts Service.
See 'systemctl status accounts-daemon.service' for details.
[FAILED] Failed to start apache2.service - The Apache HTTP Server.
See 'systemctl status apache2.service' for details.
[  OK  ] Started nginx.service - LSB: starts the nginx web server.
[FAILED] Failed to start systemd-logind.service - User Login Management.
See 'systemctl status systemd-logind.service' for details.
[  OK  ] Started dbus.service - D-Bus System Message Bus.
[FAILED] Failed to start redis-server.service - Advanced key-value store.
See 'systemctl status redis-server.service' for details.
[  OK  ] Finished systemd-user-sessions.service - Permit User Sessions.
         Starting plymouth-quit-wait.service - Hold until boot process finishes up...
         Starting plymouth-quit.service - Terminate Plymouth Boot Screen...
         Starting systemd-logind.service - User Login Management...
[  OK  ] Finished plymouth-quit-wait.service - Hold until boot process finishes up.
[  OK  ] Started console-getty.service - Console Getty.
[  OK  ] Started container-getty@1.service - Container Getty on /dev/tty1.
[  OK  ] Started container-getty@2.service - Container Getty on /dev/tty2.
[  OK  ] Reached target getty.target - Login Prompts.
[FAILED] Failed to start systemd-logind.service - User Login Management.
See 'systemctl status systemd-logind.service' for details.
         Starting systemd-logind.service - User Login Management...
[  OK  ] Finished plymouth-quit.service - Terminate Plymouth Boot Screen.
[FAILED] Failed to start systemd-logind.service - User Login Management.
See 'systemctl status systemd-logind.service' for details.
         Starting systemd-logind.service - User Login Management...
[FAILED] Failed to start systemd-logind.service - User Login Management.
See 'systemctl status systemd-logind.service' for details.
         Starting systemd-logind.service - User Login Management...
[FAILED] Failed to start systemd-logind.service - User Login Management.
See 'systemctl status systemd-logind.service' for details.
[FAILED] Failed to start systemd-logind.service - User Login Management.
See 'systemctl status systemd-logind.service' for details.
[  OK  ] Started unattended-upgrades.service - Unattended Upgrades Shutdown.
         Starting redis-server.service - Advanced key-value store...
[FAILED] Failed to start redis-server.service - Advanced key-value store.
See 'systemctl status redis-server.service' for details.
[  OK  ] Started rsyslog.service - System Logging Service.
[  OK  ] Started networkd-dispatcher.service - Dispatcher daemon for systemd-networkd.
[FAILED] Failed to start systemd-logind.service - User Login Management.
See 'systemctl status systemd-logind.service' for details.
         Starting redis-server.service - Advanced key-value store...
[FAILED] Failed to start redis-server.service - Advanced key-value store.
See 'systemctl status redis-server.service' for details.
[  OK  ] Started postfix@-.service - Postfix Mail Transport Agent (instance -).
         Starting postfix.service - Postfix Mail Transport Agent...
[  OK  ] Finished postfix.service - Postfix Mail Transport Agent.
[  OK  ] Reached target multi-user.target - Multi-User System.
[  OK  ] Reached target graphical.target - Graphical Interface.
         Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
[  OK  ] Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
 
Last edited:
Using pct enter I can see some logs, as found below, anything obvious here?


Bash: 
2024-09-18T13:21:09.430604+00:00 nextcloud systemd[1]: Starting systemd-logind.service - User Login Management...
2024-09-18T13:21:09.437400+00:00 nextcloud (d-logind)[1898]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
2024-09-18T13:21:09.438191+00:00 nextcloud systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE
2024-09-18T13:21:09.438380+00:00 nextcloud systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
2024-09-18T13:21:09.438593+00:00 nextcloud systemd[1]: Failed to start systemd-logind.service - User Login Management.
2024-09-18T13:21:09.439971+00:00 nextcloud systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 4.
2024-09-18T13:21:09.440309+00:00 nextcloud systemd[1]: modprobe@drm.service - Load Kernel Module drm was skipped because of an unmet condition check (ConditionCapability=CAP_SYS_MODULE).
2024-09-18T13:21:09.443449+00:00 nextcloud systemd[1]: Starting systemd-logind.service - User Login Management...
2024-09-18T13:21:09.451831+00:00 nextcloud (d-logind)[1902]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
2024-09-18T13:21:09.452725+00:00 nextcloud systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE
2024-09-18T13:21:09.452905+00:00 nextcloud systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
2024-09-18T13:21:09.453117+00:00 nextcloud systemd[1]: Failed to start systemd-logind.service - User Login Management.
2024-09-18T13:21:09.454574+00:00 nextcloud systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5.
2024-09-18T13:21:09.454915+00:00 nextcloud systemd[1]: modprobe@drm.service - Load Kernel Module drm was skipped because of an unmet condition check (ConditionCapability=CAP_SYS_MODULE).
2024-09-18T13:21:09.454961+00:00 nextcloud systemd[1]: systemd-logind.service: Start request repeated too quickly.
2024-09-18T13:21:09.455011+00:00 nextcloud systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
2024-09-18T13:21:09.455050+00:00 nextcloud systemd[1]: Failed to start systemd-logind.service - User Login Management.
2024-09-18T13:21:35.385468+00:00 nextcloud dbus-daemon[259]: [system] Activating via systemd: service name='org.freedesktop.lo

Bash: 
Sep 18 11:43:05 nextcloud dbus-daemon[156]: Unknown username "polkitd" in message bus configuration file
Sep 18 11:43:05 nextcloud dbus-daemon[156]: Unknown username "polkitd" in message bus configuration file
Sep 18 11:43:05 nextcloud dbus-daemon[156]: [system] Reloaded configuration
Sep 18 11:43:05 nextcloud dbus-daemon[156]: Unknown username "polkitd" in message bus configuration file
Sep 18 11:43:05 nextcloud dbus-daemon[156]: Unknown username "polkitd" in message bus configuration file
Sep 18 11:43:05 nextcloud dbus-daemon[156]: [system] Reloaded configuration
Sep 18 11:43:08 nextcloud systemd[1]: Reloading.
Sep 18 11:43:08 nextcloud systemd[1]: Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inacc
essible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 18 11:43:08 nextcloud systemd[1]: polkit.service: Current command vanished from the unit file, execution of the command li
st won't be resumed.
Sep 18 11:43:08 nextcloud systemd[1]: apt-daily-upgrade.timer: Deactivated successfully.
Sep 18 11:43:08 nextcloud systemd[1]: Stopped Daily apt upgrade and clean activities.
Sep 18 11:43:08 nextcloud systemd[1]: Stopping Daily apt upgrade and clean activities...
Sep 18 11:43:08 nextcloud systemd[1]: Started Daily apt upgrade and clean activities.
Sep 18 11:43:08 nextcloud systemd[1]: apt-daily.timer: Deactivated successfully.
Sep 18 11:43:08 nextcloud systemd[1]: Stopped Daily apt download activities.
Sep 18 11:43:08 nextcloud systemd[1]: Stopping Daily apt download activities...
Sep 18 11:43:08 nextcloud systemd[1]: Started Daily apt download activities.
Sep 18 11:43:08 nextcloud dbus-daemon[156]: Unknown username "polkitd" in message bus configuration file

Bash: 
Sep 18 11:43:15 nextcloud systemd[1]: Reloading.
Sep 18 11:43:15 nextcloud systemd[1]: /lib/systemd/system/systemd-udevd.service:21: Unknown key name 'DelegateSubgroup' in sec
tion 'Service', ignoring.
Sep 18 11:43:15 nextcloud systemd[1]: /lib/systemd/system/systemd-udevd.service:22: Failed to parse service type, ignoring: no
tify-reload
Sep 18 11:43:15 nextcloud systemd[1]: /lib/systemd/system/systemd-networkd.service:51: Failed to parse service type, ignoring:
 notify-reload
Sep 18 11:43:15 nextcloud systemd[1]: Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inacc
essible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 18 11:45:44 nextcloud systemd[1]: Reloading requested from client PID 169137 ('systemctl') (unit session-24616.scope)...
Sep 18 11:45:44 nextcloud systemd[1]: Reloading...
Sep 18 11:45:44 nextcloud (sd-gens)[169147]: Read-only bind remount failed, ignoring: Permission denied
Sep 18 11:45:44 nextcloud systemd[1]: Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 18 11:45:44 nextcloud systemd[1]: Reloading finished in 152 ms.
Sep 18 11:45:44 nextcloud systemd[1]: Reloading requested from client PID 169179 ('systemctl') (unit session-24616.scope)...
Sep 18 11:45:44 nextcloud systemd[1]: Reloading...
Sep 18 11:45:44 nextcloud kernel: [2757365.201031] audit: type=1400 audit(1726659944.664:4417): apparmor="DENIED" operation="mount" class="mount" info="failed perms check" error=-13 profile="lxc-106_</var/lib/lxc>" name="/" pid=2542722 comm="(sd-gens)" flags="ro, remount, bind"
Sep 18 11:45:44 nextcloud (sd-gens)[169189]: Read-only bind remount failed, ignoring: Permission denied
Sep 18 11:45:44 nextcloud systemd[1]: Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 18 11:45:44 nextcloud systemd[1]: Reloading finished in 153 ms.
Sep 18 11:45:44 nextcloud systemd[1]: uuidd.socket: Deactivated successfully.
Sep 18 11:45:44 nextcloud systemd[1]: Closed uuidd.socket - UUID daemon activation socket.
Sep 18 11:45:44 nextcloud systemd[1]: Stopping uuidd.socket - UUID daemon activation socket...
Sep 18 11:45:44 nextcloud systemd[1]: Listening on uuidd.socket - UUID daemon activation socket.
Sep 18 11:45:44 nextcloud systemd[1]: Reloading requested from client PID 169232 ('systemctl') (unit session-24616.scope)...
Sep 18 11:45:44 nextcloud systemd[1]: Reloading...
Sep 18 11:45:45 nextcloud kernel: [2757365.536004] audit: type=1400 audit(1726659944.999:4418): apparmor="DENIED" operation="mount" class="mount" info="failed perms check" error=-13 profile="lxc-106_</var/lib/lxc>" name="/dev/" pid=2542843 comm="(sd-gens)" flags="ro, remount, bind"
Sep 18 11:45:45 nextcloud kernel: [2757365.536097] audit: type=1400 audit(1726659944.999:4419): apparmor="DENIED" operation="mount" class="mount" info="failed perms check" error=-13 profile="lxc-106_</var/lib/lxc>" name="/" pid=2542843 comm="(sd-gens)":

Bash: 
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987199650Z" level=error msg="failed to load cni during init, please check CRI plugin status before setting up network for pods" error="cni config load failed: no network config found in /etc/cni/net.d: cni plugin not initialized: failed to load cni config"
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987332389Z" level=info msg="Start subscribing containerd event"
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987392645Z" level=info msg="Start recovering state"
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987450238Z" level=info msg="Start event monitor"
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987475141Z" level=info msg="Start snapshots syncer"
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987486703Z" level=info msg="Start cni network conf syncer for default"
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987495551Z" level=info msg="Start streaming server"
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987533130Z" level=info msg=serving... address=/run/containerd/containerd.sock.ttrpc
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987597995Z" level=info msg=serving... address=/run/containerd/containerd.sock
Sep 18 11:45:45 nextcloud containerd[169344]: time="2024-09-18T11:45:45.987677174Z" level=info msg="containerd successfully booted in 0.033923s"
Sep 18 11:45:45 nextcloud systemd[1]: Started containerd.service - containerd container runtime.
Sep 18 11:45:46 nextcloud systemd[1]: Reloading requested from client PID 169387 ('systemctl') (unit session-24616.scope)...
Sep 18 11:45:46 nextcloud systemd[1]: Reloading...
Sep 18 11:45:46 nextcloud (sd-gens)[169397]: Read-only bind remount failed, ignoring: Permission denied
Sep 18 11:45:46 nextcloud kernel: [2757367.187655] audit: type=1400 audit(1726659946.651:4421): apparmor="DENIED" operation="mount" class="mount" info="failed perms check" error=-13 profile="lxc-106_</var/lib/lxc>" name="/" pid=2543245 comm="(sd-gens)" flags="ro, remount, bind"
 
Update: The container obviously does boot as I can enter it from the host, but various major services are failing to start and I cannot find why:

[FAILED] Failed to start systemd-sysctl.service - Apply Kernel Variables.
[FAILED] Failed to start systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully.
[FAILED] Failed to start systemd-networkd.service - Network Configuration.
[FAILED] Failed to start systemd-resolved.service - Network Name Resolution
 
Yes same here. I made a fresh install of debian 12 as LXC under Proxmox 8.2.5
pveversion delivers
pve-manager/8.2.5/12c0a59769080547 (running kernel: 6.8.12-2-pve)

My LXC is a privileged because i am using it as nfs server for several other services.
Following this guide i set it up as new / fresh LXC
https://forum.proxmox.com/threads/nfs-server-in-lxc.105073/

nfs-kernel-server / exportfs is working as expected but as my previous posters allready said there are several systemd-xxx services not running.
dbus and libpam packages are all properly installed!
Bildschirmfoto vom 2024-09-23 06-34-12.png

Bildschirmfoto vom 2024-09-23 06-35-08.png


i installed webmin on all my vm / lxc so a picture from my services
Bildschirmfoto vom 2024-09-23 06-25-52.png

checking journalctl -xeu systemd-logind.service gives the following

Bildschirmfoto vom 2024-09-23 06-27-51.png

every login is deferred for several soconds.

journalctl -xeu systemd-sysctl delivers
Bildschirmfoto vom 2024-09-23 06-31-24.png

As said it's a fresh install from 22.09.2024 so can't be any "upgrade" errors from a previous version.

Any help appreciated.
 
Last edited:
ShaunG said:
@hopeITworks go to options for the container, then features, then enable "nesting", this will fix your issue.
Click to expand...
Thanks for the tip but maybe i did something wrong ...

i have checked this

Bildschirmfoto vom 2024-09-23 10-10-25.png
Bildschirmfoto vom 2024-09-23 10-10-50.png

After a server shutdown and Re-Start i still get those messages

Bildschirmfoto vom 2024-09-23 10-09-55.png

a try to start them manually is answered by:
Bildschirmfoto vom 2024-09-23 10-09-36.png

My SysLog says:
Bildschirmfoto vom 2024-09-23 10-18-21.png

What else could be the clue?
 
Last edited:
@hopeITworks Hmm that was suggested here and fixed the issue for me. Unsure if enabling this on a live container would effect things or not, I think my container was stopped when I enabled it.
 
I can't figure out what is wrong with the CT, so i decided to build a new one from scratch.
Yes, more steps to do but maybe i made a mistake by starting the CT the first time before i've set the tags in the options area.

No i have to set the following
Bildschirmfoto vom 2024-09-23 16-53-27.png

mount=nfs AND nesting=1

Both together set before i start the new CT the first time get the systemd services working so far :)

Will make a template with that now for the other CT ..

Thanks for help
 
I confirm the problem and I confirm that setting up just
nesting=1
On "Options/Features", it works like a charm (even on a newly upgraded and "apparently dead" container)
 
Last edited:
  • Like
Reactions: lorenzobrazuna
You must log in or register to reply here.
Top Bottom