lxc-stop does not shut down container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
Vivid |
Fix Released
|
Medium
|
Unassigned | ||
Wily |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for "real iron" systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default.
For the record, in upstart we had /etc/init/
https:/
SRU TEST CASE:
--------------
- Create a vivid LXC container (system or unprivileged)
- Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected.
REGRESSION POTENTIAL:
-------
- This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only.
- There is no change for VMs or "real" hardware.
tags: | added: systemd-boot |
Changed in systemd (Ubuntu Wily): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Vivid): | |
importance: | Undecided → Medium |
description: | updated |
Changed in systemd (Ubuntu Wily): | |
status: | New → In Progress |
assignee: | nobody → Martin Pitt (pitti) |
description: | updated |
description: | updated |
Fix for Debian/wily: http:// anonscm. debian. org/cgit/ pkg-systemd/ systemd. git/commit/ ?h=experimental &id=44c3369f97b
Backported for vivid: http:// anonscm. debian. org/cgit/ pkg-systemd/ systemd. git/commit/ ?h=ubuntu- vivid&id= 7c45c5bc168df