Thanks for looking at this, Martin. Minor correction: I work with Ubuntu 14.04. Containers are Wily.
> I suppose your journal output in comment #6 was from *after* you did "lxc > stop"? Correct, it was *after* "lxc stop" (resp. all the other variants) >>> lxc exec test -- ls -l >>> /lib/systemd/system/sigpwr.target.wants/sigpwr-container-shutdown.service >>> /lib/systemd/system/sigpwr-container-shutdown.service -rw-r--r-- 1 root root 153 Oct 15 11:34 /lib/systemd/system/sigpwr-container-shutdown.service lrwxrwxrwx 1 root root 36 Oct 15 12:02 /lib/systemd/system/sigpwr.target.wants/sigpwr-container-shutdown.service -> ../sigpwr-container-shutdown.service >>> lxc exec test -- systemd-detect-virt lxc >>> lxc stop test ^C>>>lxc exec test -- systemctl status -l sigpwr-container-shutdown.service ^C The last call basically hangs (also without the -l option). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: [systemd] SIGPWR doesn't always lead to shutdown Status in lxd package in Ubuntu: Triaged Status in systemd package in Ubuntu: Incomplete Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
