touch-packages team mailing list archive

[Erkan Yanar <erkan.yanar@xxxxxxxxxxxxx>]

So you run a newer version?
plus.google.com/112206451048767236518/posts/SYAueyXHeEX


Regards
Erkan


On Tue, Jun 02, 2015 at 10:57:46AM -0000, Martin Pitt wrote:
> 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 subscribed to the bug
> report.
> 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

-- 
über den grenzen muß die freiheit wohl wolkenlos sein

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