summaryrefslogtreecommitdiff
path: root/docs/podman-container-cleanup.1.md
diff options
context:
space:
mode:
authorbaude <bbaude@redhat.com>2019-02-21 17:09:59 -0600
committerbaude <bbaude@redhat.com>2019-02-22 14:13:08 -0600
commit6ab6e2c3073d47755d441ee8c1bce90e34082e99 (patch)
tree38b123449c3b4270acec7f680b688ddb2c502204 /docs/podman-container-cleanup.1.md
parent328250e7bef56b0b69dbea124c1170abd289900f (diff)
downloadpodman-6ab6e2c3073d47755d441ee8c1bce90e34082e99.tar.gz
podman-6ab6e2c3073d47755d441ee8c1bce90e34082e99.tar.bz2
podman-6ab6e2c3073d47755d441ee8c1bce90e34082e99.zip
hide --latest on the remote-client
in the case of the remote-client, it was decided to hide the latest flag to avoid confusion for end-users on what the "last" container, volume, or pod are. Signed-off-by: baude <bbaude@redhat.com>
Diffstat (limited to 'docs/podman-container-cleanup.1.md')
-rw-r--r--docs/podman-container-cleanup.1.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/podman-container-cleanup.1.md b/docs/podman-container-cleanup.1.md
index 2819d1138..e375c12ec 100644
--- a/docs/podman-container-cleanup.1.md
+++ b/docs/podman-container-cleanup.1.md
@@ -19,6 +19,9 @@ Cleanup all containers.
**--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.
+
## EXAMPLE
`podman container cleanup mywebserver`