Thanks, Stephen, culprit found. The systemd cgroup was yours - until
you did a sudo.
For now you can work around this by commenting out the libpam-cgfs line
from /etc/pam.d/common-session-noninteractive. Then re-chown your
current systemd cgroup to yourself or log back in.
I'm not yet sure whether the proper fix will be to
1. remove the line from noninteractive,
2. have libpam-cgfs check for user-$loginuid.slice in the current systemd
cgroup, and create a new one if it doesn't match
3. just add another libpam-cgfs argument to say whether to create a new systemd
cgroup, and have it not do so for noninteractive.
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Also affects: lxcfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxcfs (Ubuntu)
Importance: Undecided => High
** Changed in: lxcfs (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556447
Title:
lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
systemd controller mountpoint found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
