Merge pull request #7353 from rhatdan/v2.0

Cleanup handling of podman mount/unmount

1 files changed, 55 insertions, 0 deletions

diff --git a/docs/source/markdown/podman-unmount.1.md b/docs/source/markdown/podman-unmount.1.md
new file mode 100644
index 000000000..47c55cc0b
--- /dev/null
+++ b/docs/source/markdown/podman-unmount.1.md
@@ -0,0 +1,55 @@
+% podman-unmount(1)
+
+## NAME
+podman\-unmount - Unmount a working container's root filesystem
+
+## SYNOPSIS
+**podman unmount** [*options*] *container* [...]
+
+**podman umount** [*options*] *container* [...]
+
+**podman container unmount** [*options*] *container* [...]
+
+**podman container umount** [*options*] *container* [...]
+
+## DESCRIPTION
+Unmounts the specified containers' root file system, if no other processes
+are using it.
+
+Container storage increments a mount counter each time a container is mounted.
+When a container is unmounted, the mount counter is decremented, and the
+container's root filesystem is physically unmounted only when the mount
+counter reaches zero indicating no other processes are using the mount.
+An unmount can be forced with the --force flag.
+
+## OPTIONS
+**--all**, **-a**
+
+All of the currently mounted containers will be unmounted.
+
+**--force**, **-f**
+
+Force the unmounting of specified containers' root file system, even if other
+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.
+
+The latest option is not supported on the remote client.
+
+## EXAMPLE
+
+podman container unmount containerID
+
+podman unmount containerID1 containerID2 containerID3
+
+podman unmount --all
+
+## SEE ALSO
+podman(1), podman-container-mount(1), podman-image-mount(1)