[systemd-bugs] [Bug 90104] New: 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

            Bug ID: 90104
           Summary: systemd-nspawn: Spawning a shell in a container does
                    not work
           Product: systemd
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: registo.mailling at gmail.com
        QA Contact: systemd-bugs at lists.freedesktop.org

As the summary says, spawning a shell in a container does not work but works if
running from a command line.

I have a service file to launch a centos container and it was working with
systemd 218. After the update to systemd 219 it stopped working.

The .service file used the following ExecStart line:
/usr/bin/systemd-nspawn --keep-unit --machine=centos --link-journal=no
--bind=/home/centos:/home --tmpfs=/tmp:mode=1777 --network-bridge=brkvm
--directory=/virt/containers/centos

When trying to start the container I get the following in the journal:

> journalctl -b -u centos -o cat
Started CentOS Container.
Starting CentOS Container...
Spawning container centos on /virt/containers/centos.
Press ^] three times within 1s to kill container.
Stopping CentOS Container...
Stopped CentOS Container.

If I use the same invocation (except --keep-unit) on a command line I am able
to get a shell inside the container.

-- 
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/20150419/95085c7b/attachment.html>