lxc-stop reboots, cleanly shuts down, or kills all the processes
inside the container. By default, it will request a clean shutdown of
the container by sending lxc.haltsignal (defaults to SIGPWR) to the
container's init process, waiting up to 60 seconds for the container
to exit, and then returning. If the container fails to cleanly exit
in 60 seconds, it will be sent the lxc.stopsignal (defaults to
SIGKILL) to force it to shut down. A request to reboot will send the
lxc.rebootsignal (defaults to SIGINT) to the container's init
The [-W], [-r], [-k] and [--nokill] options specify the action to
perform. [-W] indicates that after performing the specified action,
lxc-stop should immediately exit, while [-t TIMEOUT] specifies the
maximum amount of time to wait for the container to complete the
shutdown or reboot.
Request a reboot of the container.
Rather than requesting a clean shutdown of the container,
explicitly kill all tasks in the container. This is the legacy
Only request a clean shutdown, do not kill the container tasks
if the clean shutdown fails.
This option avoids the use of any of the API lxc locking, and
should only be used if lxc-stop is hanging due to a bad system
Simply perform the requestion action (reboot, shutdown, or
hard kill) and exit.
Wait TIMEOUT seconds before hard-stopping the container.
This page is part of the lxc (Linux containers) project. Information
about the project can be found at ⟨http://linuxcontainers.org/⟩. If
you have a bug report for this manual page, send it to
firstname.lastname@example.org. This page was obtained from the
project's upstream Git repository ⟨git://github.com/lxc/lxc⟩ on
2017-03-13. If you discover any rendering problems in this HTML ver‐
sion of the page, or you believe there is a better or more up-to-date
source for the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original man‐
ual page), send a mail to email@example.com