Recent content by kenren98

Anyone with the same issue?

Also about the other one with similar issue, I saw that one too, but it seems reboot didnt solve my problem. journalctl -b -u lxcfs; systemctl status lxcfs root@node5:~# journalctl -b -u lxcfs; systemctl status lxcfs -- Journal begins at Tue 2022-10-11 16:26:17 EDT, ends at Wed 2023-04-05...

aa-status root@node5:~# aa-status apparmor module is loaded. 14 profiles are loaded. 14 profiles are in enforce mode. /usr/bin/lxc-start /usr/bin/man /usr/sbin/chronyd lsb_release lxc-container-default lxc-container-default-cgns lxc-container-default-with-mounting...

root@node5:~# pveversion -v proxmox-ve: 7.4-1 (running kernel: 5.15.104-1-pve) pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a) pve-kernel-5.15: 7.4-1 pve-kernel-5.15.104-1-pve: 5.15.104-1 pve-kernel-5.15.102-1-pve: 5.15.102-1 pve-kernel-5.15.85-1-pve: 5.15.85-1 pve-kernel-5.15.83-1-pve...

no sure if this helps found there is no apparmor folder in lxc folder

The only non-pve package I installed is lm-sensors, as far as I recall.

INFO cgfsng - ../src/lxc/cgroups/cgfsng.c:unpriv_systemd_create_scope:1227 - Running privileged, not using a systemd unit DEBUG seccomp - ../src/lxc/seccomp.c:parse_config_v2:656 - Host native arch is [3221225534] INFO seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing...