| Summary: | systemd-nspawn: restarting from inside container results in systemd-nspawn@ service deactivation | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Jonathan Liu <net147> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Container journal | ||
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.
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.