[systemd-devel] systemd-nspawn

[Chir0n]

Although I have a 3.8.5 kernel (Fedora 18) and util-linux package
installed, I don't have the nsenter binary.

Running the host with audit=0 it worked fine, however, the network
functions are working weird, but I think this is another problem.

Thank you very much.


On Mon, Apr 15, 2013 at 3:48 PM, Zbigniew Jędrzejewski-Szmek <
zbyszek at in.waw.pl> wrote:

> On Mon, Apr 15, 2013 at 08:36:33PM +0200, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Mon, Apr 15, 2013 at 02:31:56PM -0300, Chir0n wrote:
> > > # yum -y --releasever=19 --nogpg --installroot=/srv/mycontainer
> > > --disablerepo='*' --enablerepo=fedora install systemd passwd yum
> > > fedora-release vim-minimal
> > > # systemd-nspawn -bD
> > > /srv/mycontainer
> >
> >   sudo nsenter -t $PID -m -u -i -n -p /bin/bash
> Hm, if I say 'halt' in this bash window, I see
>
> bash-4.2# halt
> bash-4.2# [1]  + 14306 suspended (signal)  sudo nsenter -t 13221 -m -u -i
> -n -p /bin/bash
>
> and the container's init hangs after 'All filesystems unmounted.'.
>
> Only when I do 'fg', halt resume and systemd-nspawn quits.
>
> Apparrently only happens rarely (1/5 so far).
>
> What's going on?
>
> Zbyszek
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20130415/83056cd0/attachment.html>