I've just updated to the latest LXC version, 3.2.1.20191211, and two of my LXC containers stopped working. Both of them have systemd, one is a Centos 7.5 and the other one is an Ubuntu 16.04. I'm also running some Alpine Linux containers which work without any problem. Reverting to LXC 3.0.4 solved the issue.
The error I'm getting in the container's console:
Failed to insert module 'autofs4'
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Detected virtualization lxc.
Detected architecture x86-64.
Welcome to CentOS Linux 7 (Core)
Set hostname to <fever-backend>.
Failed to read AF_UNIX datagram queue length, ignoring: No such file or directory
Cannot determine cgroup we are running in: No such file or directory
Failed to allocate manager object: No such file or directory
!!!!!!Failed to allocate manager object, freezing.
Question
niltsiar
Hi,
I've just updated to the latest LXC version, 3.2.1.20191211, and two of my LXC containers stopped working. Both of them have systemd, one is a Centos 7.5 and the other one is an Ubuntu 16.04. I'm also running some Alpine Linux containers which work without any problem. Reverting to LXC 3.0.4 solved the issue.
The error I'm getting in the container's console:
Can anyone shed some light on the issue?
Thx
Link to comment
Share on other sites
1 answer to this question
Recommended Posts