summaryrefslogtreecommitdiff
path: root/docs/source/markdown/podman-unmount.1.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/source/markdown/podman-unmount.1.md')
-rw-r--r--docs/source/markdown/podman-unmount.1.md10
1 files changed, 7 insertions, 3 deletions
diff --git a/docs/source/markdown/podman-unmount.1.md b/docs/source/markdown/podman-unmount.1.md
index 47c55cc0b..97780111a 100644
--- a/docs/source/markdown/podman-unmount.1.md
+++ b/docs/source/markdown/podman-unmount.1.md
@@ -22,12 +22,16 @@ 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**, **-a**
All of the currently mounted containers will be unmounted.
-**--force**, **-f**
+#### **--force**, **-f**
Force the unmounting of specified containers' root file system, even if other
processes have mounted it.
@@ -35,7 +39,7 @@ 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**
+#### **--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