Hm, when I do this it seems to be correct:
$ sudo systemd-nspawn -b -D /tmp/schroot-wily-systemd/
"machinectl status schroot-wily-systemd" shows
Unit: machine-schroot\x2dwily\x2dsystemd.scope
├─12745 /lib/systemd/systemd
[...]
and systemd-cgls shows
├─machine.slice
│ └─machine-schroot\x2dwily\x2dsystemd.scope
│ ├─12745 /lib/systemd/systemd
│ └─system.slice
[...]
If I run nspawn with --slice foo.slice I get
├─foo.slice
│ └─machine-schroot\x2dwily\x2dsystemd.scope
│ ├─12876 /lib/systemd/systemd
[...]
>From what command is the output in the description?
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455828
Title:
machinctl/systemd-nspawn containers/processes end in wrong slice
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1455828/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
