Bug#903288: systemd-container: container does not reboot when it is started by machinectl or systemctl,Re: Bug#903288: systemd-container: container does not reboot when it is started by machinectl or

Control: tags -1 + upstream It turns out to be an upsteam bug standing for two years... https://github.com/systemd/systemd/issues/9540#issuecomment-403342632

Bug#903288: systemd-container: container does not reboot when it is started by machinectl or systemctl,Re: Bug#903288: systemd-container: container does not reboot when it is started by machinectl or

Control: forwarded -1 https://github.com/systemd/systemd/issues/9540 Hi Michael, Thanks for your quick response. I reported this to the upstream as above. Ryutaroh From: Michael Biebl Date: Sun, 8 Jul 2018 19:28:08 +0200 > We don't really ship any Debian specific patches in that regard, so it

Bug#903288: systemd-container: container does not reboot when it is started by machinectl or systemctl

Hi Am 08.07.2018 um 14:44 schrieb Ryutaroh Matsumoto: > A systemd-nspawn container does not reboot if it is started by > machinectl or systemctl on the host Linux. The key error messages are We don't really ship any Debian specific patches in that regard, so it would be great if you can file

Bug#903288: systemd-container: container does not reboot when it is started by machinectl or systemctl

Package: systemd-container Version: 239-5 Severity: normal A systemd-nspawn container does not reboot if it is started by machinectl or systemctl on the host Linux. The key error messages are Jul 08 21:17:17 unstable systemd[1]: Starting Container container-unstable... Jul 08 21:17:17 unstable