mirror of
https://github.com/containers/podman.git
synced 2025-10-27 19:34:13 +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>
16 lines
817 B
Markdown
16 lines
817 B
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.
|
|
#### **--group-add**=*group* | *keep-groups*
|
|
|
|
Assign additional groups to the primary user running within the container process.
|
|
|
|
- `keep-groups` is a special flag that tells Podman to keep the supplementary group access.
|
|
|
|
Allows container to use the user's supplementary group access. If file systems or
|
|
devices are only accessible by the rootless user's group, this flag tells the OCI
|
|
runtime to pass the group access into the container. Currently only available
|
|
with the `crun` OCI runtime. Note: `keep-groups` is exclusive, you cannot add any other groups
|
|
with this flag. (Not available for remote commands, including Mac and Windows (excluding WSL2) machines)
|