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

[Marshall2, John (SSC/SPC)]

Hi,

So I have started trying out 2.1.1 but have encountered a different issue.

I have the following:
/sys/fs/cgroup/<controllers>/
jobs/
cgroup.clone_children (= 0)
xx/
cgroup.clone_children (= 1)
cpusets.cpus (= 1)
cpusets.mems (= 0-1)

In the config file I have:
lxc.cgroup.dir = jobs/xx

As before, I want lxc-start to set up its own cgroup inside jobs/xx (e.g., at
jobs/xx/xx where the container name is "xx"), but inherit the settings from
jobs/xx.

I find that this is not working. Also, unexpectedly, jobs/cgroup.clone_children
is being reset to 1, which I do not want.

Is there any way to force lxc-start to just inherit and not touch anything else?

Thanks,
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/20180301/d86e19ed/attachment.html>