Can you give some more details on the version of:
- lxd package on the host
- liblxc1 package on the host
- lxcfs package on the host
- Ubuntu version in the container
- systemd version in the container
And confirm that:
- This behavior is reproducible for you with the following steps:
lxd-images import ubuntu (wily or xenial) --alias ubuntu
lxc launch ubuntu test
sleep 10s
lxc stop test
- Executing "shutdown" manually inside the container (through lxc exec) does shutdown the container
- Manually doing "kill -SIGPWR <PID>" where <PID> is the init pid as reported by "lxc info test", also doesn't shutdown the container for you.
With those we should have a better idea of where the bug (seems systemd is most likely) and we'll triage accordingly.
Can you give some more details on the version of:
- lxd package on the host
- liblxc1 package on the host
- lxcfs package on the host
- Ubuntu version in the container
- systemd version in the container
And confirm that:
- This behavior is reproducible for you with the following steps:
lxd-images import ubuntu (wily or xenial) --alias ubuntu
lxc launch ubuntu test
sleep 10s
lxc stop test
- Executing "shutdown" manually inside the container (through lxc exec) does shutdown the container
- Manually doing "kill -SIGPWR <PID>" where <PID> is the init pid as reported by "lxc info test", also doesn't shutdown the container for you.
With those we should have a better idea of where the bug (seems systemd is most likely) and we'll triage accordingly.
Thanks!