New Privileged Container No Console

Z

zamadatix

New Member
Sep 27, 2024
1
2
3
On Proxmox VE 8.2.7 I've grabbed the latest Ubuntu and Arch containers:

archlinux-base_20240911-1_amd64.tar.zst
ubuntu-24.04-standard_24.04-2_amd64.tar.zst

And tried deploying them with "unprivileged container" unchecked. On starting the containers and going to the Console tab the console never loads. Setting an IP the address never pings, like the container isn't completing the launch. I see the same behavior on multiple hosts. Deploying the container with "unprivileged container" left checked will work fine.
 
  • Like
Reactions: dasaweb and timurprox
Bumping this one - I'm running into the same problem on 8.2.7. I'm able to create containers, both unprivileged or privileged, but the console only ever connects to the unprivileged ones.

If I SSH into the Proxmox host and use pct to enter the container, I can see the following errors:

Code: 
root@proxmox-4:/etc/pve/lxc# pct start 131
root@proxmox-4:/etc/pve/lxc# pct enter 131
root@canbus:/# journalctl -p err -b 0
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
Nov 09 03:07:38 canbus (networkd)[93]: systemd-networkd.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus (networkd)[99]: systemd-networkd.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus (networkd)[105]: systemd-networkd.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus (networkd)[117]: systemd-networkd.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus (tmpfiles)[118]: systemd-tmpfiles-setup.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
Nov 09 03:07:38 canbus (resolved)[135]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus (networkd)[130]: systemd-networkd.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus (resolved)[149]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus (resolved)[165]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus (resolved)[176]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus (resolved)[188]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus systemd[1]: Failed to start apparmor.service - Load AppArmor profiles.
Nov 09 03:07:38 canbus (d-logind)[244]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus (d-logind)[284]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus (d-logind)[296]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus (d-logind)[314]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus (d-logind)[332]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus rsyslogd[323]: file '/var/log/syslog': open error: Permission denied [v8.2312.0 try https://www.rsyslog.com/e/2433 ]
Nov 09 03:07:39 canbus (agetty)[278]: container-getty@1.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[276]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[281]: container-getty@2.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[452]: container-getty@2.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[451]: container-getty@1.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[457]: container-getty@2.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[456]: container-getty@1.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[460]: container-getty@1.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[461]: container-getty@2.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[463]: container-getty@1.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[465]: container-getty@2.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus systemd[1]: Failed to start container-getty@1.service - Container Getty on /dev/tty1.
Nov 09 03:07:39 canbus systemd[1]: Failed to start container-getty@2.service - Container Getty on /dev/tty2.
Nov 09 03:07:39 canbus (agetty)[468]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[470]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[472]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:40 canbus (agetty)[474]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:40 canbus systemd[1]: Failed to start console-getty.service - Console Getty.
 
  • Like
Reactions: timurprox
  • Like
Reactions: reidesuka, F1NN and CoryS
Same here using Proxmox 8.3.4 with ubuntu-24.04-standard_24.04-2_amd64: needs Nesting ON.

But, debian-12-standard_12.7-1_amd64 works with Nesting OFF.

:oops:
 
You must log in or register to reply here.
Top Bottom