blob: 31a213f28af4918599faa615e8cd4b66fb25430b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
% 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)
|
