opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-06-23 18:59:30 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #15809 from edsantiago/docs_dedup_user

Browse Source 
[CI:DOCS] Man pages: refactor common options: --user
This commit is contained in:
OpenShift Merge Robot
2022-09-14 21:50:21 +02:00
committed by GitHub
parent 9b6cb7e80f f76390d5e6
commit bb4872e2f6
4 changed files with 10 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/source/markdown/options/user.md Normal file
View File

@ -0,0 +1,7 @@
#### **--user**, **-u**=*user[:group]*
Sets the username or UID used and, optionally, the groupname or GID for the specified command. Both *user* and *group* may be symbolic or numeric.
Without this argument, the command will run as the user specified in the container image. Unless overridden by a `USER` command in the Containerfile or by a value passed to this option, this user generally defaults to root.
When a user namespace is not in use, the UID and GID used within the container and on the host will match. When user namespaces are in use, however, the UID and GID in the container may correspond to another UID and GID on the host. In rootless containers, for example, a user namespace is always used, and root in the container will by default correspond to the UID and GID of the user invoking Podman.

9
docs/source/markdown/podman-create.1.md.in
View File

@ -450,14 +450,7 @@ When size is `0`, there is no limit on the amount of memory used for IPC by the
@@option unsetenv-all @@option unsetenv-all
#### **--user**, **-u**=*user* @@option user
Sets the username or UID used and optionally the groupname or GID for the specified command.
The following examples are all valid:
--user [user | user:group | uid | uid:gid | user:gid | uid:group ]
Without this argument the command will be run as root in the container.
@@option userns.container @@option userns.container

6
docs/source/markdown/podman-exec.1.md.in
View File

@ -44,11 +44,7 @@ to run containers such as CRI-O, the last started container could be from either
@@option tty @@option tty
#### **--user**, **-u** @@option user
Sets the username or UID used and optionally the groupname or GID for the specified command.
The following examples are all valid:
--user [user | user:group | uid | uid:gid | user:gid | uid:group ]
@@option workdir @@option workdir

8
docs/source/markdown/podman-run.1.md.in
View File

@ -491,13 +491,7 @@ echo "asdf" | podman run --rm -i someimage /bin/cat
@@option unsetenv-all @@option unsetenv-all
#### **--user**, **-u**=*user[:group]* @@option user
Sets the username or UID used and, optionally, the groupname or GID for the specified command. Both *user* and *group* may be symbolic or numeric.
Without this argument, the command will run as the user specified in the container image. Unless overridden by a `USER` command in the Containerfile or by a value passed to this option, this user generally defaults to root.
When a user namespace is not in use, the UID and GID used within the container and on the host will match. When user namespaces are in use, however, the UID and GID in the container may correspond to another UID and GID on the host. In rootless containers, for example, a user namespace is always used, and root in the container will by default correspond to the UID and GID of the user invoking Podman.
@@option userns.container @@option userns.container