hi,
I'm experiencing the same problem. I use "lxc.cgroup" to constrain resource usage and to provide access to devices

in trying to re-use containers established under Trusty, I find that lxc.cgroup clauses prevent the container starting

furthermore, if I create a new "test" container on Xenial, it will start and run ok until I start adding lxc.cgroup clauses, at which point it will no longer start.

LXC is installed. LXD is NOT installed. CGMANAGER is installed. All packages are current from Xenial LTS

Is there anything I can do to help pin this down ? Will a test conducted in a KVM based VM be valid / useful ?

Rob

On 27/06/16 11:41, Serge E. Hallyn wrote:
Quoting Mike Wright ([email protected]):
On 06/26/2016 01:01 PM, Serge E. Hallyn wrote:
Quoting Mike Wright ([email protected]):
Hi all,

cgmanager and cgmanager-utils are installed.

Environment is ubuntu-xenial, lxc-2.0.1, cgm-0.29
why 0.29?  xenial should have 0.39-2ubuntu5.  I'm on xenial
using 0.41-2~ubuntu16.04.1~ppa1 from the ubuntu-lxc
ppa.
Thanks for the response, Serge.

This is interesting.

sudo apt install -s cgmanager
   cgmanager is already the newest version (0.39-2ubuntu5)

cgm --version
   0.29

Added ppa:ubuntu-lxc/stable, updated and upgraded.

sudo apt install -s cgmanager
   cgmanager is already the newest version (0.41-2~ubuntu16.04.1~ppa1)

cgm --version
   0.29
Oh, huh.  Yeah, that seems to be a cgmanager bug :)

0 ✓ serge@sl ~ $ sudo cgm create all me
[sudo] password for serge:
0 ✓ serge@sl ~ $ sudo cgm chown all me $(id -u) $(id -g)
0 ✓ serge@sl ~ $

Now, I'm not running systemd so it's possible systemd is
doing something unorthodox again.  But really it sounds
like a bug that shouldve been fixed in 0.27-0ubuntu6 -
where cgmanager didn't deal well with comounted controllers.
Still failing at cgm chown...

Ideas on how would I go about determining the problem?
Edit /lib/systemd/system/cgmanager.service and add '--debug' to the
end of the ExecStart line.  Do 'systemctl daemon-reload' followed
by 'systemctl restart cgmanager'.  Then do the above again, and
do 'journalctl -u cgmanager' and list the results here.  Also
show the contents of /proc/self/cgroup and /proc/self/mountinfo.
That should give us what we need.

thanks,
-serge
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users

_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users

Reply via email to