[Bug 1436044] [NEW] cgproxy in systemd (vivd) containers doesn't work

[Serge Hallyn]

Public bug reported:

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.

** Affects: cgmanager (Ubuntu)
     Importance: High
         Status: Fix Released

** Affects: cgmanager (Ubuntu Trusty)
     Importance: High
         Status: New

** Affects: cgmanager (Ubuntu Utopic)
     Importance: High
         Status: New

** Also affects: cgmanager (Ubuntu Utopic)
   Importance: Undecided
       Status: New

** Also affects: cgmanager (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: cgmanager (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: cgmanager (Ubuntu Utopic)
   Importance: Undecided => High

** Changed in: cgmanager (Ubuntu)
   Importance: Undecided => High

** Changed in: cgmanager (Ubuntu)
       Status: New => Fix Released

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

Title:
  cgproxy in systemd (vivd) containers doesn't work

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