Bug 80811 - systemd-nspawn: restarting from inside container results in systemd-nspawn@ service deactivation
Summary: systemd-nspawn: restarting from inside container results in systemd-nspawn@ s...
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-02 14:49 UTC by Jonathan Liu
Modified: 2014-07-03 11:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Container journal (17.39 KB, text/plain)
2014-07-02 14:49 UTC, Jonathan Liu 		Details
View All

Description Jonathan Liu 2014-07-02 14:49:42 UTC 
Created attachment 102137 [details]
Container journal

I have systemd-nspawn@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@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.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.