From d12489858d69be0dbe6495c24440bcd293de1001 Mon Sep 17 00:00:00 2001 From: Erik Sjölund Date: Fri, 18 Feb 2022 08:04:30 +0100 Subject: [CI:DOCS] troubleshooting: mention overlay option for --rootfs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Mention overlay option for --rootfs. Overlay description text is from commit 020d81f113ea1e11398ea77495cc4b8e05a91d38 by Qi Wang Signed-off-by: Erik Sjölund --- troubleshooting.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) (limited to 'troubleshooting.md') 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 -- cgit v1.2.3-54-g00ecf