podman/podman-unmount.1.md at 4b427df80c118a25d1a8c173f194edd54853ed97

mirror of https://github.com/containers/podman.git synced 2025-07-28 19:02:48 +08:00

Files

Paul Holzinger bc48211924 Fix long option format on docs.podman.io

Escape the two dashes, otherwise they are combined into one long dash.
I tested that this change is safe and still renders correctly on github
and with the man pages.

This commit also contains a small change to make it build locally.
Assuming you have the dependencies installed you can do:
```
cd docs
make html
```
Preview the html files in docs/build/html with
`python -m http.server 8000 --directory build/html`.

Fixes containers/podman.io#373

Signed-off-by: Paul Holzinger <paul.holzinger@web.de>

2021-03-29 14:38:25 +02:00

1.8 KiB

Raw Blame History

% podman-unmount(1)

NAME

podman-unmount - Unmount a working container's root filesystem

SYNOPSIS

podman unmount [options] container [...]

podman umount [options] container [...]

podman container unmount [options] container [...]

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

Note: Podman can be used to unmount Podman containers as well as external containers. External containers are containers created in container/storage by other tools like Buildah and CRI-O.

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. (This option is not available with the remote Podman client)

EXAMPLE

podman container unmount containerID

podman unmount containerID1 containerID2 containerID3

podman unmount --all

1.8 KiB Raw Blame History