On Mon, Jun 02, 2014 at 11:47:39AM +1000, Jonathan Liu wrote: > Hi, > > I am using systemd 212 on Arch Linux 64-bit with the following patch applied: > http://cgit.freedesktop.org/systemd/systemd/commit/?id=d8e40d62ab871a87fde421c4b246bb45bc3cbe2d It would be easy for us if you could test the latest systemd 213
> 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. And without the above patch ? (perhaps some cleaning races/left jobs...) > Any ideas on how to proceed with fixing it so the container isn't > killed when reboot is issued inside the container? If you are able to disable the service, try running it manually: # systemd-nspawn -bD /path/to/container Taken from: https://wiki.archlinux.org/index.php/Arch_systemd_container Then do a reboot/restart from the container and see! If this works, then it may be related to the service logic, otherwise it's just the container config or systemd-nspawn... And please do past some container logs. If time permits, I'll try to test it later. Thanks! > Regards, > Jonathan > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Djalal Harouni http://opendz.org _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel