mirror of https://github.com/containers/podman.git
docs: update podman-wait man page
Waiting now actually makes sure to exit on first container exit. Also notice that it does not wait for --rm to have the container removed at this point. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
This commit is contained in:
parent
94fd5fe6f7
commit
6fb10421fb
|
@ -16,10 +16,13 @@ separated by newline in the same order as they were given to the command. An
|
|||
exit code of -1 is emitted for all conditions other than "stopped" and
|
||||
"exited".
|
||||
|
||||
NOTE: there is an inherent race condition when waiting for containers with a
|
||||
restart policy of `always` or `on-failure`, such as those created by `podman
|
||||
kube play`. Such containers may be repeatedly exiting and restarting, possibly
|
||||
with different exit codes, but `podman wait` can only display and detect one.
|
||||
When waiting for containers with a restart policy of `always` or `on-failure`,
|
||||
such as those created by `podman kube play`, the containers may be repeatedly
|
||||
exiting and restarting, possibly with different exit codes. `podman wait` will
|
||||
only display and detect the first exit after the wait command was started.
|
||||
|
||||
When running a container with podman run --rm wait should wait for the
|
||||
container to be fully removed as well before it returns.
|
||||
|
||||
## OPTIONS
|
||||
|
||||
|
|
Loading…
Reference in New Issue