mirror of
https://github.com/containers/podman.git
synced 2025-06-10 01:31:58 +08:00
beb71323b1
podman-generate and -play had the wrong NAMEs.
podman-restart and -volume-prune the wrong SYNOPSIS.
All the rest are varying degrees of minor:
- missing a space between the NAME and description
- multi-line SYNOPSIS that could be collapsed into one
- use of UPPER CASE in synopsis instead of *asterisks*
- improper use of **double asterisks** for options
- varlink and version were transposed in podman-1
- fixed inconsistencies between the description in
the man page and that in the parent manpage. These
are too numerous for me to fix all.
Added: script that could be used in CI to prevent future
such inconsistencies. It cannot be enabled yet because
there are still 35+ inconsistencies in need of cleaning.
This will be difficult to review on github. I suggest
pulling the PR and running 'git log -1 -p | cdif | less'
'cdif' is a handy tool for colorizing individual diffs between
lines:
http://kaz-utashiro.github.io/cdif/
There are other such tools; use your favorite. Comparing
without visual highlights may be painful.
I also encourage you to run hack/man-page-checker and suggest
more fixes for the problems it's finding.
Signed-off-by: Ed Santiago <santiago@redhat.com>
67 lines
1.7 KiB
Markdown
67 lines
1.7 KiB
Markdown
% podman-restart(1)
|
|
|
|
## NAME
|
|
podman\-restart - Restart one or more containers
|
|
|
|
## SYNOPSIS
|
|
**podman restart** [*options*] *container* ...
|
|
|
|
## DESCRIPTION
|
|
The restart command allows containers to be restarted using their ID or name.
|
|
Containers will be stopped if they are running and then restarted. Stopped
|
|
containers will not be stopped and will only be started.
|
|
|
|
## OPTIONS
|
|
**--all, -a**
|
|
Restart all containers regardless of their current state.
|
|
|
|
**--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.
|
|
|
|
The latest option is not supported on the remote client.
|
|
|
|
**--running**
|
|
Restart all containers that are already in the *running* state.
|
|
|
|
**--timeout**
|
|
Timeout to wait before forcibly stopping the container.
|
|
|
|
|
|
## EXAMPLES ##
|
|
|
|
Restart the latest container
|
|
```
|
|
$ podman restart -l
|
|
ec588fc80b05e19d3006bf2e8aa325f0a2e2ff1f609b7afb39176ca8e3e13467
|
|
```
|
|
|
|
Restart a specific container by partial container ID
|
|
```
|
|
$ podman restart ff6cf1
|
|
ff6cf1e5e77e6dba1efc7f3fcdb20e8b89ad8947bc0518be1fcb2c78681f226f
|
|
```
|
|
|
|
Restart two containers by name with a timeout of 4 seconds
|
|
```
|
|
$ podman restart --timeout 4 test1 test2
|
|
c3bb026838c30e5097f079fa365c9a4769d52e1017588278fa00d5c68ebc1502
|
|
17e13a63081a995136f907024bcfe50ff532917988a152da229db9d894c5a9ec
|
|
```
|
|
|
|
Restart all running containers
|
|
```
|
|
$ podman restart --running
|
|
```
|
|
|
|
Restart all containers
|
|
```
|
|
$ podman restart --all
|
|
```
|
|
|
|
## SEE ALSO
|
|
podman(1), podman-run(1), podman-start(1), podman-create(1)
|
|
|
|
## HISTORY
|
|
March 2018, Originally compiled by Matt Heon <mheon@redhat.com>
|