2019-05-31 19:21:47 +00:00
|
|
|
% podman-umount(1)
|
2017-12-15 21:58:36 +00:00
|
|
|
|
|
|
|
## NAME
|
2019-08-30 14:09:50 +00:00
|
|
|
podman\-umount - Unmount a working container's root filesystem
|
2017-12-15 21:58:36 +00:00
|
|
|
|
|
|
|
## SYNOPSIS
|
2019-05-31 19:21:47 +00:00
|
|
|
**podman umount** *container* [...]
|
2017-12-15 21:58:36 +00:00
|
|
|
|
2019-08-31 20:58:52 +00:00
|
|
|
**podman container umount** *container* [...]
|
|
|
|
|
|
|
|
**podman container unmount** *container* [...]
|
|
|
|
|
|
|
|
**podman unmount** *container* [...]
|
|
|
|
|
2017-12-15 21:58:36 +00:00
|
|
|
## DESCRIPTION
|
2018-07-30 13:04:18 +00:00
|
|
|
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.
|
2018-06-27 17:34:10 +00:00
|
|
|
|
|
|
|
## OPTIONS
|
2019-05-31 19:21:47 +00:00
|
|
|
**--all**, **-a**
|
2018-06-27 17:34:10 +00:00
|
|
|
|
|
|
|
All of the currently mounted containers will be unmounted.
|
2017-12-15 21:58:36 +00:00
|
|
|
|
2019-05-31 19:21:47 +00:00
|
|
|
**--force**, **-f**
|
2018-07-30 13:04:18 +00:00
|
|
|
|
|
|
|
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.
|
|
|
|
|
2019-05-31 19:21:47 +00:00
|
|
|
**--latest**, **-l**
|
2019-01-15 22:08:54 +00:00
|
|
|
|
|
|
|
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.
|
|
|
|
|
2019-02-21 23:09:59 +00:00
|
|
|
The latest option is not supported on the remote client.
|
|
|
|
|
2017-12-15 21:58:36 +00:00
|
|
|
## EXAMPLE
|
|
|
|
|
|
|
|
podman umount containerID
|
|
|
|
|
2018-06-27 17:34:10 +00:00
|
|
|
podman umount containerID1 containerID2 containerID3
|
|
|
|
|
|
|
|
podman umount --all
|
|
|
|
|
2017-12-15 21:58:36 +00:00
|
|
|
## SEE ALSO
|
|
|
|
podman(1), podman-mount(1)
|