[Bug 1467611] Re: unprivileged lxc containers broken

[Serge Hallyn]

The cgmanager log shows:

Invalid path /run/cgmanager/fs/none,name=systemd/system.slice/lsh-
server.service/lxc/asterisk

How are you logged in when you try to start the container?

To start an unprivileged container, you must be logged into a regular
user session, so /proc/self/cgroup should look something like:


10:memory:/user.slice/user-1000.slice/session-c2.scope
9:perf_event:/user.slice/user-1000.slice/session-c2.scope
8:cpu,cpuacct:/user.slice/user-1000.slice/session-c2.scope
7:cpuset:/user.slice/user-1000.slice/session-c2.scope
6:net_cls,net_prio:/user.slice/user-1000.slice/session-c2.scope
5:blkio:/user.slice/user-1000.slice/session-c2.scope
4:hugetlb:/user.slice/user-1000.slice/session-c2.scope
3:devices:/user.slice/user-1000.slice/session-c2.scope
2:freezer:/user.slice/user-1000.slice/session-c2.scope
1:name=systemd:/user.slice/user-1000.slice/session-c2.scope

Instead you seem to be in /system.slice/lsh-server.service, which
you do not own.  So as an unprivileged user you cannot create
new cgroups for yourself, which is why lxc is failing.


** Also affects: lxc (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: lxc (Ubuntu)
       Status: New => Incomplete

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1467611

Title:
  unprivileged lxc containers broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1467611/+subscriptions