login into unprivileged trusty containers fail to get own name=systemd cgroup
Bug #1543353 reported by
Serge Hallyn
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lxc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| lxcfs (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
libpam-cgfs expects systemd to create the name=systemd cgroup.
However, on trusty with upstart that does not happen. So the logged-in
user doesn't get his own name=systemd cgroup.
It's not entirely clear where this should be fixed. Putting the logic into libpam-cgfs may be fragile.
Revision history for this message
| Serge Hallyn (serge-hallyn) wrote | #1 |
| Changed in lxcfs (Ubuntu): | |
| status: | New → Confirmed |
| status: | Confirmed → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Serge Hallyn (serge-hallyn) wrote | #2 |
| Changed in lxcfs (Ubuntu): | |
| status: | Triaged → Fix Released |
| Changed in lxc (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
lxc currently puts 'name=systemd' into its list of controllers which must be available for the user. That's not always the case. Again it's not clear what the best thing to do there is.