cgproxy in systemd (vivd) containers doesn't work
Bug #1436044 reported by
Serge Hallyn
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cgmanager (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
| Trusty |
Invalid
|
High
|
Unassigned | ||
Bug Description
systemd starts cgproxy inside a slice, meaning it is not in pid 1's cgroup and not an ancestor of tasks who ask it to act.
This means that for a systemd container to have a useful cgproxy, cgmanager on the host must make an exception for cgproxy being in its default slice.
| Changed in cgmanager (Ubuntu Trusty): | |
| importance: | Undecided → High |
| Changed in cgmanager (Ubuntu Utopic): | |
| importance: | Undecided → High |
| Changed in cgmanager (Ubuntu): | |
| importance: | Undecided → High |
| status: | New → Fix Released |
Revision history for this message
| Serge Hallyn (serge-hallyn) wrote | #1 |
| no longer affects: | cgmanager (Ubuntu Utopic) |
| Changed in cgmanager (Ubuntu Trusty): | |
| status: | New → Invalid |
To post a comment you must log in.
Actually this isn't valid unless and until lxcfs is in the archive for trusty, which may never happen.