On 20/01/16 18:59, Carlos Alberto Lopez Perez wrote:
> Hello,
>
> I've found that when lxc-autostart is executed via systemd, the cgroups
> assigned to the container are wrong for some control groups.
>
> See the following two examples:
>
> 1. Container started via systemd (/lib/systemd/system/lxc.service unit
> that calls lxc-autostart).
>
> # cat /proc/${pidofsomeprocessinsidethecontainer}/cgroup
> 9:perf_event:/lxc/clopeztest3
> 8:blkio:/
> 7:net_cls,net_prio:/lxc/clopeztest3
> 6:freezer:/lxc/clopeztest3
> 5:devices:/
> 4:memory:/
> 3:cpu,cpuacct:/
> 2:cpuset:/lxc/clopeztest3
> 1:name=systemd:/system.slice/lxc.service
>
>
After more testing, this only seems reproducible when booting.
If I manually execute via ssh:
# systemctl stop lxc
# systemctl start lxc
Then the cgroups assigned to the container are correct:
# cat /proc/${pidofsomeprocessinsidethecontainer}/cgroup
9:perf_event:/lxc/clopeztest3
8:blkio:/lxc/clopeztest3
7:net_cls,net_prio:/lxc/clopeztest3
6:freezer:/lxc/clopeztest3
5:devices:/lxc/clopeztest3
4:memory:/lxc/clopeztest3
3:cpu,cpuacct:/lxc/clopeztest3
2:cpuset:/lxc/clopeztest3
1:name=systemd:/system.slice/lxc.service
signature.asc
Description: OpenPGP digital signature
_______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
