podman/docs/podman-umount.1.md at c285bd664e2a61562ff31778029f4cab7d931a5b

mirror of https://github.com/containers/podman synced 2024-10-21 01:34:37 +00:00

Daniel J Walsh 8e1ef558eb Add --force to podman umount to force the unmounting of the rootfs

podman umount will currently only unmount file system if not other
process is using it, otherwise the umount decrements the container
storage to indicate that the caller is no longer using the mount
point, once the count gets to 0, the file system is actually unmounted.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

Closes: #1184
Approved by: TomSweeneyRedHat

2018-08-01 17:53:30 +00:00

1.1 KiB

Raw Blame History

% podman-umount "1"

NAME

podman-umount - Unmount the specified working containers' root file system.

SYNOPSIS

podman umount 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.

EXAMPLE

podman umount containerID

podman umount containerID1 containerID2 containerID3

podman umount --all

1.1 KiB Raw Blame History