1ff45aac40
Updates the stop.md doc to mention that the stop signal can be changed, either with the Dockerfile or via `docker run --stop-signal`. This is a real gotcha if you're not familiar with this feature and build a container that extends a container that uses `STOPSIGNAL`.
Signed-off-by: Christopher Vermilion <christopher.vermilion@gmail.com>
(cherry picked from commit 41d169d211)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
31 lines
657 B
Markdown
31 lines
657 B
Markdown
---
|
|
title: "stop"
|
|
description: "The stop command description and usage"
|
|
keywords: "stop, SIGKILL, SIGTERM"
|
|
---
|
|
|
|
# stop
|
|
|
|
```markdown
|
|
Usage: docker stop [OPTIONS] CONTAINER [CONTAINER...]
|
|
|
|
Stop one or more running containers
|
|
|
|
Options:
|
|
--help Print usage
|
|
-t, --time int Seconds to wait for stop before killing it (default 10)
|
|
```
|
|
|
|
## Description
|
|
|
|
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`.
|
|
|
|
## Examples
|
|
|
|
```bash
|
|
$ docker stop my_container
|
|
```
|