diff options
author | baude <bbaude@redhat.com> | 2019-10-24 14:54:57 -0500 |
---|---|---|
committer | baude <bbaude@redhat.com> | 2019-10-31 12:31:39 -0500 |
commit | 52b92023edeba3a5e2c466d92d742e54b14a85cb (patch) | |
tree | 44e6193d49afd1277b7d07b0df41fc80d31b3adb /docs/podman-umount.1.md | |
parent | 5af166ff513265b17aee92a9ce3a1522090d7dec (diff) | |
download | podman-52b92023edeba3a5e2c466d92d742e54b14a85cb.tar.gz podman-52b92023edeba3a5e2c466d92d742e54b14a85cb.tar.bz2 podman-52b92023edeba3a5e2c466d92d742e54b14a85cb.zip |
Restructure documentation dir
Restructuring the docs dir to make integration with sphinx easier. man
pages now exist in docs/source/man and the sphinx make files exists in
docs.
Signed-off-by: baude <bbaude@redhat.com>
Diffstat (limited to 'docs/podman-umount.1.md')
-rw-r--r-- | docs/podman-umount.1.md | 55 |
1 files changed, 0 insertions, 55 deletions
diff --git a/docs/podman-umount.1.md b/docs/podman-umount.1.md deleted file mode 100644 index 100c47b32..000000000 --- a/docs/podman-umount.1.md +++ /dev/null @@ -1,55 +0,0 @@ -% podman-umount(1) - -## NAME -podman\-umount - Unmount a working container's root filesystem - -## SYNOPSIS -**podman umount** *container* [...] - -**podman container umount** *container* [...] - -**podman container unmount** *container* [...] - -**podman unmount** *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 umount containerID - -podman umount containerID1 containerID2 containerID3 - -podman umount --all - -## SEE ALSO -podman(1), podman-mount(1) |