summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2022-02-21 11:15:41 -0500
committerGitHub <noreply@github.com>2022-02-21 11:15:41 -0500
commitcd00a99c66b7be750655f396269499a78cdc4e2c (patch)
tree2e56d8a1409c156e85c584879144d9efbdf22012
parentd224a0f8ac4978c3ac399a0940f785892d63daa8 (diff)
parentd12489858d69be0dbe6495c24440bcd293de1001 (diff)
downloadpodman-cd00a99c66b7be750655f396269499a78cdc4e2c.tar.gz
podman-cd00a99c66b7be750655f396269499a78cdc4e2c.tar.bz2
podman-cd00a99c66b7be750655f396269499a78cdc4e2c.zip
Merge pull request #13284 from eriksjolund/troubleshooting_mention_rootfs_overlay_option
[CI:DOCS] troubleshooting: mention overlay option for --rootfs
-rw-r--r--troubleshooting.md14
1 files changed, 12 insertions, 2 deletions
diff --git a/troubleshooting.md b/troubleshooting.md
index 6f2a96a56..426c4b5ce 100644
--- a/troubleshooting.md
+++ b/troubleshooting.md
@@ -645,16 +645,26 @@ to mount volumes on them.
Run the container once in read/write mode, Podman will generate all of the FDs on the rootfs, and
from that point forward you can run with a read-only rootfs.
+```
$ podman run --rm --rootfs /path/to/rootfs true
+```
The command above will create all the missing directories needed to run the container.
After that, it can be used in read only mode, by multiple containers at the same time:
+```
$ podman run --read-only --rootfs /path/to/rootfs ....
+```
+
+Another option is to use an Overlay Rootfs Mount:
+
+```
+$ podman run --rootfs /path/to/rootfs:O ....
+```
-Another option would be to create an overlay file system on the directory as a lower and then
-then allow podman to create the files on the upper.
+Modifications to the mount point are destroyed when the container
+finishes executing, similar to a tmpfs mount point being unmounted.
### 26) Running containers with CPU limits fails with a permissions error