[Bug 1455828] Re: machinctl/systemd-nspawn containers/processes end in wrong slice

[Martin Pitt]

No, I'm running what is in Ubuntu 15.10 (not too different from 15.04),
and we don't have that patch yet. Anyway, if that helps (you can easily
apply it locally), that clarifies this matter for sure. :-) Thanks for
digging out the link!

** Changed in: systemd (Ubuntu)
       Status: Incomplete => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1455828

Title:
  machinctl/systemd-nspawn containers/processes end in wrong slice

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Starting a Container via systemd-nspawn it is supposed to run in the machine.slice.
  While on Fedora 21 (systemd 216) it works like expected. 

  In Unbuntu 15.04 (systemd 219)

  Slice=system-systemd\x5cx2dnspawn.slice
  ControlGroup=/system.slice/system-systemd\x5cx2dnspawn.slice/systemd-nspawn at jessie02.service

  On Fedora 21:
  Slice=machine.slice
  ControlGroup=/machine.slice/machine-jessie.scope

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