2016-10-14 18:30:36 -04:00
|
|
|
---
|
|
|
|
title: "stop"
|
|
|
|
description: "The stop command description and usage"
|
2016-11-03 18:48:30 -04:00
|
|
|
keywords: "stop, SIGKILL, SIGTERM"
|
2016-10-14 18:30:36 -04:00
|
|
|
---
|
2015-06-21 16:41:38 -04:00
|
|
|
|
|
|
|
# stop
|
|
|
|
|
2016-07-07 14:43:18 -04:00
|
|
|
```markdown
|
|
|
|
Usage: docker stop [OPTIONS] CONTAINER [CONTAINER...]
|
2015-06-21 16:41:38 -04:00
|
|
|
|
2016-07-07 14:43:18 -04:00
|
|
|
Stop one or more running containers
|
2015-06-21 16:41:38 -04:00
|
|
|
|
2016-07-07 14:43:18 -04:00
|
|
|
Options:
|
|
|
|
--help Print usage
|
|
|
|
-t, --time int Seconds to wait for stop before killing it (default 10)
|
|
|
|
```
|
2015-06-21 16:41:38 -04:00
|
|
|
|
2017-02-07 18:42:48 -05:00
|
|
|
## Description
|
|
|
|
|
2015-06-21 16:41:38 -04:00
|
|
|
The main process inside the container will receive `SIGTERM`, and after a grace
|
2021-04-03 17:13:01 -04:00
|
|
|
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`.
|
2017-02-07 18:42:48 -05:00
|
|
|
|
|
|
|
## Examples
|
|
|
|
|
2021-08-21 08:54:14 -04:00
|
|
|
```console
|
2017-02-07 18:42:48 -05:00
|
|
|
$ docker stop my_container
|
|
|
|
```
|