touch-packages team mailing list archive

[Erkan Yanar <erkan.yanar@xxxxxxxxxxxxx>]

The documentation claims machine.slice is the default.

man systemd-nspawn:
       --slice=
           Make the container part of the specified slice, instead of the default machine.slice

The machine.slice although still exists. So It is a doku bug? Is there a
changlog telling it is going to change?

Regards
Erkan

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete

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@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