[lxc-users] forcing a container to use a specific cgroup with v2.0.8

[Marshall2, John (SSC/SPC)]

I did not find a solution with 2.0.8, so I moved on to 2.1. The lxc.cgroup.dir seems to do
what I want. Unfortunately, the cgroup configuration process seems to change settings
outside of the cgroup/dir pointed to be lxc.cgroup.dir, namely, sets cgroup.clone_children
to 1 when it should be 0.

I have asked about this latter issue on the lxc forum at
https://discuss.linuxcontainers.org/t/why-cgroups-are-setup-as-they-are/1313/2

John

On Wed, 2018-02-28 at 22:58 +0000, Marshall2, John (SSC/SPC) wrote:
Hi,

At the moment I am using LXC 2.0.8 (ubuntu 16.04) and have noticed a change in behavior
since previous releases of LXC I have used (1.x and 2.0.5, I believe). I've not yet narrowed
when the change happened.

My goal is to start an LXC container within an existing (arbitrary) cgroup. Previously, I was
able to run lxc-start from within a cgroup and the new LXC cgroup would be created under
it. I used lxc.cgroup.pattern=%n in lxc.conf.

Is there any way to do the same thing with v2.0.8? I see that 2.1 has lxc.cgroup.dir which
appears to do what I need, but I am trying to do this with 2.0.8, at least for now.

Thanks,
John

_______________________________________________
lxc-users mailing list
lxc-users at lists.linuxcontainers.org<mailto:lxc-users at lists.linuxcontainers.org>
http://lists.linuxcontainers.org/listinfo/lxc-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20180302/b5eb2bc0/attachment.html>