[systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

[Dariusz Michaluk]

On 05.03.2014 19:16, Lennart Poettering wrote:
> nspawn and libvirt-lxc mostly follow the same code paths and register
> via machined... So it's weird that different things happen. Somehow the
> systemd instance inside the container must be confused about the cgroup
> it is running in...

Next few cents. I noticed that when I run lxc-libvirt container I get 
warning "Failed to install release agent, ignoring: No such file or 
directory", which does not occur when I use nspawn.

systemd 210 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA 
+SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR)
Detected virtualization 'lxc-libvirt'.
Detected architecture 'x86'.

Welcome to Fedora 21 (Rawhide)!
Failed to install release agent, ignoring: No such file or directory
[  OK  ] Reached target Remote File Systems.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Reached target Swap.
[  OK  ] Created slice Root Slice.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Listening on Journal Socket.
[  OK  ] Created slice System Slice.
...

-- 
Dariusz Michaluk
Samsung R&D Institute Poland
Samsung Electronics
d.michaluk at samsung.com