mirror of
https://github.com/containers/podman.git
synced 2025-06-03 12:17:13 +08:00
bc48211924
Escape the two dashes, otherwise they are combined into one long dash. I tested that this change is safe and still renders correctly on github and with the man pages. This commit also contains a small change to make it build locally. Assuming you have the dependencies installed you can do: ``` cd docs make html ``` Preview the html files in docs/build/html with `python -m http.server 8000 --directory build/html`. Fixes containers/podman.io#373 Signed-off-by: Paul Holzinger <paul.holzinger@web.de>
66 lines
2.0 KiB
Markdown
66 lines
2.0 KiB
Markdown
% podman-stop(1)
|
|
|
|
## NAME
|
|
podman\-stop - Stop one or more running containers
|
|
|
|
## SYNOPSIS
|
|
**podman stop** [*options*] *container* ...
|
|
|
|
**podman container stop** [*options*] *container* ...
|
|
|
|
## DESCRIPTION
|
|
Stops one or more containers. You may use container IDs or names as input. The **\-\-time** switch
|
|
allows you to specify the number of seconds to wait before forcibly stopping the container after the stop command
|
|
is issued to the container. The default is 10 seconds. By default, containers are stopped with SIGTERM
|
|
and then SIGKILL after the timeout. The SIGTERM default can be overridden by the image used to create the
|
|
container and also via command line when creating the container.
|
|
|
|
## OPTIONS
|
|
|
|
#### **\-\-all**, **-a**
|
|
|
|
Stop all running containers. This does not include paused containers.
|
|
|
|
#### **\-\-cidfile**
|
|
|
|
Read container ID from the specified file and remove the container. Can be specified multiple times.
|
|
|
|
#### **\-\-ignore**, **-i**
|
|
|
|
Ignore errors when specified containers are not in the container store. A user
|
|
might have decided to manually remove a container which would lead to a failure
|
|
during the ExecStop directive of a systemd service referencing that container.
|
|
|
|
#### **\-\-latest**, **-l**
|
|
|
|
Instead of providing the container name or ID, use the last created container. If you use methods other than Podman
|
|
to run containers such as CRI-O, the last started container could be from either of those methods. (This option is not available with the remote Podman client)
|
|
|
|
#### **\-\-time**, **-t**=*time*
|
|
|
|
Time to wait before forcibly stopping the container
|
|
|
|
## EXAMPLES
|
|
|
|
$ podman stop mywebserver
|
|
|
|
$ podman stop 860a4b235279
|
|
|
|
$ podman stop mywebserver 860a4b235279
|
|
|
|
$ podman stop --cidfile /home/user/cidfile-1
|
|
|
|
$ podman stop --cidfile /home/user/cidfile-1 --cidfile ./cidfile-2
|
|
|
|
$ podman stop --time 2 860a4b235279
|
|
|
|
$ podman stop -a
|
|
|
|
$ podman stop --latest
|
|
|
|
## SEE ALSO
|
|
podman(1), podman-rm(1)
|
|
|
|
## HISTORY
|
|
September 2018, Originally compiled by Brent Baude <bbaude@redhat.com>
|