docker container stop [OPTIONS] CONTAINER [CONTAINER...] Aliases
An alias is a short or memorable alternative for a longer command.
docker stop
The main process inside the container will receive SIGTERM, and after a grace period, SIGKILL. The first signal can be changed with the STOPSIGNAL instruction in the container's Dockerfile, or the --stop-signal option to docker run and docker create.
-s, --signal Signal to send to the container -t, --timeout Seconds to wait before killing the container Stop container with signal (-s, --signal)
The --signal flag sends the system call signal to the container to exit. This signal can be a signal name in the format SIG<NAME>, for instance SIGKILL, or an unsigned number that matches a position in the kernel's syscall table, for instance 9. Refer to signal(7) for available signals.
The default signal to use is defined by the image's StopSignal, which can be set through the STOPSIGNAL Dockerfile instruction when building the image, or configured using the --stop-signal option when creating the container. If no signal is configured for the container, SIGTERM is used as default.
The --timeout flag sets the number of seconds to wait for the container to stop after sending the pre-defined (see [--signal]{#signal)) system call signal. If the container does not exit after the timeout elapses, it's forcibly killed with a SIGKILL signal.
If you set --timeout to -1, no timeout is applied, and the daemon waits indefinitely for the container to exit.
The default timeout can be specified using the --stop-timeout option when creating the container. If no default is configured for the container, the Daemon determines the default, and is 10 seconds for Linux containers, and 30 seconds for Windows containers.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4