summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2019-02-09 05:33:14 -0700
committerDaniel J Walsh <dwalsh@redhat.com>2019-02-09 05:33:14 -0700
commit233ba5bd894aac77db1bb2e41b0ef464f865d2a0 (patch)
treee937c8b78b0bc53374fa45f94e909582ed2c402c /docs
parent1fd9be022fc1484c9bdebfc41008d2344237073c (diff)
downloadpodman-233ba5bd894aac77db1bb2e41b0ef464f865d2a0.tar.gz
podman-233ba5bd894aac77db1bb2e41b0ef464f865d2a0.tar.bz2
podman-233ba5bd894aac77db1bb2e41b0ef464f865d2a0.zip
Remove container from storage on --force
Currently we can get into a state where a container exists in storage but does not exist in libpod. If the user forces a removal of this container, then we should remove it from storage even if the container is owned by another tool. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/podman-rm.1.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/podman-rm.1.md b/docs/podman-rm.1.md
index 4fcb0b6c5..f4513c2be 100644
--- a/docs/podman-rm.1.md
+++ b/docs/podman-rm.1.md
@@ -17,7 +17,9 @@ Remove all containers. Can be used in conjunction with -f as well.
**--force, f**
-Force the removal of a running and paused containers
+Force the removal of running and paused containers. Forcing a containers removal also
+removes containers from container storage even if the container is not known to podman.
+Containers could have been created by a different container engine.
**--latest, -l**