diff options
author | Matthew Heon <mheon@redhat.com> | 2018-11-28 12:24:14 -0500 |
---|---|---|
committer | Matthew Heon <mheon@redhat.com> | 2018-12-06 09:10:45 -0500 |
commit | a0c9be20617a871c6cb61f27516565af36338d7a (patch) | |
tree | ef09e2cd5bda4a87fc6c8b3ac735cdf6615065b0 /docs | |
parent | 75b19ca8abe1957f3c48035767960a6b20c10519 (diff) | |
download | podman-a0c9be20617a871c6cb61f27516565af36338d7a.tar.gz podman-a0c9be20617a871c6cb61f27516565af36338d7a.tar.bz2 podman-a0c9be20617a871c6cb61f27516565af36338d7a.zip |
Add --sync option to podman rm
With the changes made recently to ensure Podman does not hit the
OCI runtime as often to sync state, we can find ourselves in a
situation where the runtime's state does not match ours.
Add a --sync flag to podman rm to ensure we can still remove
containers when this happens.
Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/podman-rm.1.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/podman-rm.1.md b/docs/podman-rm.1.md index 56664a8c1..7f22113ea 100644 --- a/docs/podman-rm.1.md +++ b/docs/podman-rm.1.md @@ -24,6 +24,13 @@ Remove all containers. Can be used in conjunction with -f as well. 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. +**--sync** + +Force a sync of container state with the OCI runtime before attempting to remove. +In some cases, a container's state in the runtime can become out of sync with Podman's state, +which can cause Podman to refuse to remove containers because it believes they are still running. +A sync will resolve this issue. + **--volumes, -v** Remove the volumes associated with the container. (Not yet implemented) |