On Wed, Oct 28, 2015 at 11:55:32AM +0100, Christian Brauner wrote: > On Wed, Oct 28, 2015 at 04:08:09PM +0900, Tycho Andersen wrote: > > Hi all, > > > > I'm seeing some (what seems to me to be) odd behavior, where only a > > task's init process is in its freezer cgroup: > > > > firedrill:~ sudo lxc-info -n proposed > > Name: proposed > > State: RUNNING > > PID: 10959 > > IP: 10.0.3.176 > > IP: 10.0.4.1 > > CPU use: 2.77 seconds > > BlkIO use: 0 bytes > > Memory use: 24.42 MiB > > KMem use: 0 bytes > > Link: vethM6Q3GG > > TX bytes: 1.01 KiB > > RX bytes: 3.66 KiB > > Total bytes: 4.67 KiB > > firedrill:~ cat /sys/fs/cgroup/freezer/lxc/proposed/tasks > > 10959 > > > > I vaguely recall something like this before, but I don't remember how it was > > resolved. Surely all of the tasks in the container should live in the > > freezer > > cgroup? > > > > Note that this doesn't seem to happen with LXD (even with privileged > > containers). Haven't had time to investigate further. > > Could this be by any chance related to a kernel bug? I don't see this > behaviour > at all (neither priv nor unpriv):
I suppose so; I'm on, Linux firedrill 4.2.0-10-generic #12-Ubuntu SMP Tue Sep 15 19:43:01 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux (i.e. ubuntu wily with the latest kernel + lxc). It seems odd to me that the children aren't here, but perhaps I'm misunderstanding how freezer is supposed to work. Tycho > Archlinux > Kernel 4.2.5 > lxc 1.1.4 > lxcfs 0.11 > cgmanager 0.39 > _______________________________________________ > lxc-devel mailing list > lxc-devel@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-devel _______________________________________________ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel