diff options
| author | Daniel J Walsh <dwalsh@redhat.com> | 2020-07-09 14:53:46 -0400 |
|---|---|---|
| committer | Daniel J Walsh <dwalsh@redhat.com> | 2020-07-27 16:53:02 -0400 |
| commit | 8f7ed50cb20c04bbbb7c4907a183c07912d4bffb (patch) | |
| tree | 14001f06bc0a278d0e34c6e7312ffd08c3afe526 /docs/source/markdown/podman-umount.1.md | |
| parent | 2b7bc9b101887a789a9fc0282d448efad824404f (diff) | |
| download | podman-8f7ed50cb20c04bbbb7c4907a183c07912d4bffb.tar.gz podman-8f7ed50cb20c04bbbb7c4907a183c07912d4bffb.tar.bz2 podman-8f7ed50cb20c04bbbb7c4907a183c07912d4bffb.zip | |
Cleanup handling of podman mount/unmount
We should default to the user name unmount rather then the internal
name of umount.
Also User namespace was not being handled correctly. We want to inform
the user that if they do a mount when in rootless mode that they have
to be first in the podman unshare state.
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'docs/source/markdown/podman-umount.1.md')
| -rw-r--r-- | docs/source/markdown/podman-umount.1.md | 55 |
1 files changed, 0 insertions, 55 deletions
diff --git a/docs/source/markdown/podman-umount.1.md b/docs/source/markdown/podman-umount.1.md deleted file mode 100644 index 31a213f28..000000000 --- a/docs/source/markdown/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** [*options*] *container* [...] - -**podman container umount** [*options*] *container* [...] - -**podman container unmount** [*options*] *container* [...] - -**podman unmount** [*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 umount containerID - -podman umount containerID1 containerID2 containerID3 - -podman umount --all - -## SEE ALSO -podman(1), podman-mount(1) |