docs/daemon/execdriver/lxc
Brian Goff d2c4ee37c6 Fix LXC stop signals
`lxc-stop` does not support sending arbitrary signals.
By default, `lxc-stop -n <id>` would send `SIGPWR`.
The lxc driver was always sending `lxc-stop -n <id> -k`, which always
sends `SIGKILL`. In this case `lxc-start` returns an exit code of `0`,
regardless of what the container actually exited with.
Because of this we must send signals directly to the process when we
can.

Also need to set quiet mode on `lxc-start` otherwise it reports an error
on `stderr` when the container exits cleanly (ie, we didn't SIGKILL it),
this error is picked up in the container logs... and isn't really an
error.

Also cleaned up some potential races for waitblocked test.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
2015-05-06 11:56:48 -04:00
..
driver.go Fix LXC stop signals 2015-05-06 11:56:48 -04:00
info.go Windows: Factor out LXC 2015-04-30 14:28:35 -07:00
info_test.go Windows: Factor out LXC 2015-04-30 14:28:35 -07:00
init.go Windows: Factor out LXC 2015-04-30 14:28:35 -07:00
lxc_init_linux.go Windows: Factor out LXC 2015-04-30 14:28:35 -07:00
lxc_init_unsupported.go Windows: Factor out LXC 2015-04-30 14:28:35 -07:00
lxc_template.go Feature: option for disable OOM killer 2015-05-04 21:11:29 +08:00
lxc_template_unit_test.go execdriver/lxc: use local rand.Random in test 2015-04-08 18:13:07 -07:00