[systemd-bugs] [Bug 90104] systemd-nspawn: Spawning a shell in a container does not work

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=90104

--- Comment #2 from Mauro Santos <registo.mailling at gmail.com> ---
I used to launch the container with a service file and then use nsenter to
enter the container and run more programs without needing to keep any terminals
open, something like this:

- start container
- enter container as user1 and/or user2, run vncserver for the accounts and
leave it running without any terminal windows open
- use vncviewer on the host to run graphical programs inside the container as
each user.

Before I had no need to actually boot the container, the one time I tried to
boot the container (centos5) it failed. Besides it takes a lot longer to boot
the container than to launch just a shell.

The other advantage I used to have with this, is that if the host's Xorg
crashed (or I needed to relogin for some reason) then everything inside the
container would not be affected.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150420/17cfb3ba/attachment.html>