Public bug reported:
This is on 16.04.6.
It appears that on some systems, libpam-cgfs doesn't set the correct cgroup
information, which prevents containers from starting. This can be seen by
looking at the contents of /proc/self/cgroup, which in my case was:
blkio:/user.slice
cpu,cpuacct:/user.slice
cpuset:/
devices:/user.slice
freezer:/
hugetlb:/
memory:/user.slice
name=systemd:/user.slice/user-18160.slice/session-12214.scope
net_cls,net_prio:/
perf_event:/
pids:/user.slice/user-18160.slice
whereas it should have instead of freezer:/ freezer:/user/<myusername>/0
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883041
Title:
libpam-cgfs fails to create freezer cgroup writable by user
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1883041/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
