mirror of
https://github.com/containers/podman.git
synced 2025-06-18 07:28:57 +08:00
c9c2f644da
In each options/foo.md, keep a list of where the option is used. This will be valuable to anyone making future edits, and to those reviewing those edits. This may be a controversial commit, because those crossref lists are autogenerated as a side effect of the script that reads them. It definitely violates POLA. And one day, some kind person will reconcile (e.g.) --label, using it in more man pages, and maybe forget to git-commit the rewritten file, and CI will fail. I think this is a tough tradeoff, but worth doing. Without this, it's much too easy for someone to change an option file in a way that renders it inapplicable/misleading for some podman commands. Signed-off-by: Ed Santiago <santiago@redhat.com>
24 lines
1.0 KiB
Markdown
24 lines
1.0 KiB
Markdown
####> This option file is used in:
|
|
####> podman create, run
|
|
####> If you edit this file, make sure your changes
|
|
####> are applicable to all of those.
|
|
#### **--rootfs**
|
|
|
|
If specified, the first argument refers to an exploded container on the file system.
|
|
|
|
This is useful to run a container without requiring any image management, the rootfs
|
|
of the container is assumed to be managed externally.
|
|
|
|
`Overlay Rootfs Mounts`
|
|
|
|
The `:O` flag tells Podman to mount the directory from the rootfs path as
|
|
storage using the `overlay file system`. The container processes
|
|
can modify content within the mount point which is stored in the
|
|
container storage in a separate directory. In overlay terms, the source
|
|
directory will be the lower, and the container storage directory will be the
|
|
upper. Modifications to the mount point are destroyed when the container
|
|
finishes executing, similar to a tmpfs mount point being unmounted.
|
|
|
|
Note: On **SELinux** systems, the rootfs needs the correct label, which is by default
|
|
**unconfined_u:object_r:container_file_t:s0**.
|