[lxc-devel] please open lxc-cgroup for unprivileged monitoring

Harald Dunkel harald.dunkel at aixigo.de
Mon Oct 24 08:49:04 UTC 2016


Hi Serge,

On 10/21/2016 04:56 PM, Serge E. Hallyn wrote:
> 
> lxc-cgroup talks to the container to find out the cgroup it is running
> in.  There could for instance be several containers called 'c1' (in
> different lxcpaths), which could be running in cgroups c1, c1.0, and c1.1.
> And for each controller the cgroup name could be different.

I understand that naming collisions must be taken care of, but
the current implementation just moves the problem to somewhere
else: Now everybody interested needs access to the mapping
between the container name and the cgroup path. Apparently this
became a write operation, even though a read operation should do.

sysctl performs a similar task as lxc-cgroup, and yet I don't
have to be root to run "sysctl -a". Do you think lxc-cgroup
could be modified accordingly?

Regards
Harri



More information about the lxc-devel mailing list