[systemd-bugs] [Bug 80811] New: Restarting from inside systemd-nspawn container results in deactivation

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 80811
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: Restarting from inside systemd-nspawn container
                    results in deactivation
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: net147 at gmail.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Created attachment 102137
  --> https://bugs.freedesktop.org/attachment.cgi?id=102137&action=edit
Container journal

I have systemd-nspawn at mycontainer service enabled and started for my container.
If I SSH into the container and run the reboot command, the container
reboots successfully and I can SSH into it again.
However if I run systemctl status systemd-nspawn at mycontainer on the
host, I notice the Active status changes from "Active: active
(running)" to "Active: deactivating (stop-sigterm)". After about a
minute and a half, systemd kills the container and my SSH connection
is lost.

Using systemd 213 on Arch Linux.

-- 
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/20140702/8cd98a0a/attachment-0001.html>