summaryrefslogtreecommitdiff
path: root/docs/podman-umount.1.md
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2019-01-15 17:08:54 -0500
committerDaniel J Walsh <dwalsh@redhat.com>2019-01-16 10:05:41 -0500
commit78fc4c67fdd1f8d8a3567ffd941c1f5b3e1b6ba5 (patch)
tree46e3eced8e0188d2979136ecbd87a833323f71fe /docs/podman-umount.1.md
parentd8683219d2ac5fd9a0aa271ef9d94cebe0c2adc0 (diff)
downloadpodman-78fc4c67fdd1f8d8a3567ffd941c1f5b3e1b6ba5.tar.gz
podman-78fc4c67fdd1f8d8a3567ffd941c1f5b3e1b6ba5.tar.bz2
podman-78fc4c67fdd1f8d8a3567ffd941c1f5b3e1b6ba5.zip
Add --latest and --all to podman mount/umount
I find these useful for playing around with containers. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'docs/podman-umount.1.md')
-rw-r--r--docs/podman-umount.1.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/podman-umount.1.md b/docs/podman-umount.1.md
index 70f30869a..cceb63019 100644
--- a/docs/podman-umount.1.md
+++ b/docs/podman-umount.1.md
@@ -29,6 +29,12 @@ processes have mounted it.
Note: This could cause other processes that are using the file system to fail,
as the mount point could be removed without their knowledge.
+**--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.
+
## EXAMPLE
podman umount containerID