[SOLVED] pve4 lxc arch / problems with systemd 226 in container

[ojaksch]

Clean and fresh install of pve4 at a Dell R410 for testing and discovering potentially issues when migrating from pve3.4 at main machine.Did some testing with a lxc arch-template (archlinux-base_2015-24-29-1_x86_64.tar.gz) which is working fine and fast with all dozens of packages I installed.I then did an upgrade of arch and at the moment it installs systemd/systemd-sysvcompat/libsystemd 226-3 (from 224-1), pve's syslog complains about many of

lxcfs[1018]: get_next_cgroup_dir: I was fed bad input

arch is still working, but shutting down takes many seconds (instead of klick--off) and can't be turned on anymore. When turning on container, pve's syslog is filled up with above message again.pve's syslog at the moment systemd and it's dependencys get installed:

Oct 11 12:48:03 proxmox2 kernel: [ 1343.477246] audit: type=1400 audit(1444560483.475:8): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default" name="/sys/fs/cgroup/" pid=2342 comm="systemd" flags="ro, nosuid, nodev, noexec, remount, strictatime"

Oct 11 12:48:03 proxmox2 lxcfs[1018]: get_next_cgroup_dir: I was fed bad input

Oct 11 12:48:03 proxmox2 lxcfs[1018]: get_next_cgroup_dir: I was fed bad input

[...]

I cannot get the point what going wrong there. Anyone any idea?(and sorry for that unusual format in text, but had problems with linebreaks etc)

 

[dietmar]

Anyone any idea?(and sorry for that unusual format in text, but had problems with linebreaks etc)

mounting cgroup fs is simply not allowed inside containers - that is why you get the apparmor message in the syslog.
But I never saw that lxcfs error message so far.

 

[ojaksch]

Thanks, Dietmar.Seems this is an arch-thing then IMHO, but how to stop this behaviour? I mean, I changed nothing at this container, except installing some packages, but the only service I turned to on, is sshd.

 

[ojaksch]

...seems NOT to be an arch-thing but systemd in lxc containers: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1497420So I turn down my hands for now and will keep an eye on this.

 

[dietmar]

can you reproduce the bug with the standard archlinux template we provide?

 

[ojaksch]

can you reproduce the bug with the standard archlinux template we provide?

Yes. It IS your standard archlinux template, which is working very good, including installing packages, fiddling, updating - EXCEPT updating to systemd[xx]-226.

 

[dietmar]

Yes. It IS your standard archlinux template, which is working very good, including installing packages, fiddling, updating - EXCEPT updating to systemd[xx]-226.

Please can you report a bug at bugzilla.proxmox.com?

 

[ojaksch]

Please can you report a bug at bugzilla.proxmox.com?

...done. Thanks for listening, Dietmar!

 

[ojaksch]

[solved] Re: pve4 lxc arch / problems with systemd 226 in container

As mentioned at https://bugzilla.proxmox.com/show_bug.cgi?id=755 this bug IS fixed. I waited for updated lxcfs/cgmanager packages, but either I missed that or other things were going - I set up another pve4 last weekend and created an arch-lxc today and wondered, why systemd-227 is working with lxc.However, the most important thing is that I'm very glad now.Thanks for listening and cheers!