[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

Lennart Poettering <lennart at poettering.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTABUG

--- Comment #1 from Lennart Poettering <lennart at poettering.net> ---
Hmm, if you just start a shell, then it's stdin will be connected to /dev/null,
which means it immediately gets an EOF on it. This means the shell will
immediately exit.

It's identical to invoking "/bin/sh < /dev/null" which will exit immediately
too. Or in factthe same as invoking /bin/sh as a service directly by specifying
ExecStart=/bin/sh. 

This is expected behaviour, hence.

Also, what's the usecase for this? I mean, if you just invoke a shell there's
little you can do with it anyway...

-- 
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/db1f4f07/attachment-0001.html>