Hello. New to Proxmox and LXC in general, so this is probably just some stupid user issue but after updating from v6 to v7 I've found that with any container I create, there are strange errors getting their services up. So far tried
Below are some logs related to latter one, as I suspect this default template should work without major hiccups? For me the boot takes 5 minutes (Raise network interfaces timeout, only black Console during this) and there are multiple services failing. The container is created with default settings; Unprivileged=Yes, nesting=1.
CT template and creation:
Config:
Boot messages (3 failing services)
LXC start debug log attached (due to post size limit).
Any ideas where to troubleshoot? In case this might be more problematic issue, a full reinstall of PVE is still on the table, as so far I've been only getting to know the system and testing stuff, mostly Win10 & macOS VMs. This is pretty much the first major hurdle, and looks like one I'm not able to pass
debian-10-turnkey-zoneminder_16.1-1_amd64
and the default debian-11-standard_11.0-1_amd64
.Below are some logs related to latter one, as I suspect this default template should work without major hiccups? For me the boot takes 5 minutes (Raise network interfaces timeout, only black Console during this) and there are multiple services failing. The container is created with default settings; Unprivileged=Yes, nesting=1.
Code:
~ pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.4: 6.4-7
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.4.143-1-pve: 5.4.143-1
pve-kernel-5.4.140-1-pve: 5.4.140-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-12
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-4
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.6-pve1~bpo10+1
CT template and creation:
Code:
~ pveam list local
NAME SIZE
local:vztmpl/debian-11-standard_11.0-1_amd64.tar.gz 232.15MB
*** CT creation in web UI with default options ***
extracting archive '/var/lib/vz/template/cache/debian-11-standard_11.0-1_amd64.tar.gz'
Total bytes read: 684820480 (654MiB, 81MiB/s)
Detected container architecture: amd64
Creating SSH host key 'ssh_host_ecdsa_key' - this may take some time ...
done: SHA256:... root@debian
Creating SSH host key 'ssh_host_rsa_key' - this may take some time ...
done: SHA256:Wz5/... root@debian
Creating SSH host key 'ssh_host_dsa_key' - this may take some time ...
done: SHA256:/... root@debian
Creating SSH host key 'ssh_host_ed25519_key' - this may take some time ...
done: SHA256:... root@debian
TASK OK
Config:
Bash:
~ cat /etc/pve/lxc/102.conf
arch: amd64
cores: 4
features: nesting=1
hostname: debian
memory: 2080
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=BA:D9:87:12:F3:8F,ip=dhcp,ip6=dhcp,type=veth
ostype: debian
rootfs: hdd1t:subvol-102-disk-0,size=64G
swap: 2080
unprivileged: 1
Boot messages (3 failing services)
Bash:
~ lxc-start -n 102 -F -l DEBUG -o /tmp/lxc-102.log
systemd 247.3-6 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
Detected virtualization lxc.
Detected architecture x86-64.
Welcome to Debian GNU/Linux 11 (bullseye)!
Set hostname to <debian>.
Queued start job for default target Graphical Interface.
[ OK ] Created slice system-container\x2dgetty.slice.
[ OK ] Created slice system-modprobe.slice.
[ OK ] Created slice system-postfix.slice.
[ OK ] Created slice User and Session Slice.
[ OK ] Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Started Forward Password Requests to Wall Directory Watch.
[ OK ] Reached target Local Encrypted Volumes.
[ OK ] Reached target Paths.
[ OK ] Reached target Remote Encrypted Volumes.
[ OK ] Reached target Remote File Systems.
[ OK ] Reached target Slices.
[ OK ] Reached target Swap.
[ OK ] Listening on Syslog Socket.
[ OK ] Listening on initctl Compatibility Named Pipe.
systemd-journald-audit.socket: Failed to create listening socket (audit 1): Operation not permitted
systemd-journald-audit.socket: Failed to listen on sockets: Operation not permitted
systemd-journald-audit.socket: Failed with result 'resources'.
[FAILED] Failed to listen on Journal Audit Socket.
See 'systemctl status systemd-journald-audit.socket' for details.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket.
[ OK ] Listening on Network Service Netlink Socket.
Mounting POSIX Message Queue File System...
Starting Wait for network to be configured by ifupdown...
Starting Load Kernel Module configfs...
Starting Load Kernel Module drm...
Starting Load Kernel Module fuse...
Starting nftables...
systemd-journald.service: Attaching egress BPF program to cgroup /sys/fs/cgroup/system.slice/systemd-journald.service failed: Invalid argument
Starting Journal Service...
Starting Load Kernel Modules...
Starting Remount Root and Kernel File Systems...
Starting Helper to synchronize boot up for ifupdown...
[ OK ] Mounted POSIX Message Queue File System.
modprobe@configfs.service: Succeeded.
[ OK ] Finished Load Kernel Module configfs.
modprobe@drm.service: Succeeded.
[ OK ] Finished Load Kernel Module drm.
modprobe@fuse.service: Succeeded.
[ OK ] Finished Load Kernel Module fuse.
Mounting Kernel Configuration File System...
[ OK ] Finished Remount Root and Kernel File Systems.
Starting Create System Users...
sys-kernel-config.mount: Mount process exited, code=exited, status=32/n/a
sys-kernel-config.mount: Failed with result 'exit-code'.
[FAILED] Failed to mount Kernel Configuration File System.
See 'systemctl status sys-kernel-config.mount' for details.
[ OK ] Finished Helper to synchronize boot up for ifupdown.
[ OK ] Finished nftables.
[ OK ] Reached target Network (Pre).
[ OK ] Finished Load Kernel Modules.
Starting Apply Kernel Variables...
[ OK ] Finished Create System Users.
Starting Create Static Device Nodes in /dev...
[ OK ] Finished Apply Kernel Variables.
[ OK ] Finished Create Static Device Nodes in /dev.
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting Raise network interfaces...
Starting Network Service...
[ OK ] Started Journal Service.
Starting Flush Journal to Persistent Storage...
[ OK ] Started Network Service.
Starting Wait for Network to be Configured...
[ OK ] Finished Flush Journal to Persistent Storage.
Starting Create Volatile Files and Directories...
[ OK ] Finished Wait for Network to be Configured.
[ OK ] Finished Create Volatile Files and Directories.
Starting Network Name Resolution...
[ OK ] Reached target System Time Set.
[ OK ] Reached target System Time Synchronized.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Finished Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started Periodic ext4 Online Metadata Check for All Filesystems.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Timers.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Listening on OpenBSD Secure Shell server socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
[ OK ] Started Regular background program processing daemon.
[ OK ] Started D-Bus System Message Bus.
Starting Remove Stale Online ext4 Metadata Check Snapshots...
Starting System Logging Service...
Starting User Login Management...
[ OK ] Started System Logging Service.
[ OK ] Finished Remove Stale Online ext4 Metadata Check Snapshots.
[ OK ] Started User Login Management.
[ OK ] Started Network Name Resolution.
[ OK ] Reached target Host and Network Name Lookups.
[ OK ] Finished Wait for network to be configured by ifupdown.
[** ] A start job is running for Raise network interfaces (23s / 5min) ***BOOT STUCK HERE FOR THE 5 MIN ***
[FAILED] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
Starting Postfix Mail Transport Agent (instance -)...
Starting Permit User Sessions...
[ OK ] Finished Permit User Sessions.
[ OK ] Started Console Getty.
[ OK ] Started Container Getty on /dev/tty1.
[ OK ] Started Container Getty on /dev/tty2.
[ OK ] Reached target Login Prompts.
[ OK ] Started Postfix Mail Transport Agent (instance -).
Starting Postfix Mail Transport Agent...
[ OK ] Finished Postfix Mail Transport Agent.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Finished Update UTMP about System Runlevel Changes.
Debian GNU/Linux 11 debian console
debian login:
LXC start debug log attached (due to post size limit).
Any ideas where to troubleshoot? In case this might be more problematic issue, a full reinstall of PVE is still on the table, as so far I've been only getting to know the system and testing stuff, mostly Win10 & macOS VMs. This is pretty much the first major hurdle, and looks like one I'm not able to pass