aboutsummaryrefslogtreecommitdiff
path: root/docs/source/markdown/podman-exec.1.md.in
diff options
context:
space:
mode:
Diffstat (limited to 'docs/source/markdown/podman-exec.1.md.in')
-rw-r--r--docs/source/markdown/podman-exec.1.md.in18
1 files changed, 2 insertions, 16 deletions
diff --git a/docs/source/markdown/podman-exec.1.md.in b/docs/source/markdown/podman-exec.1.md.in
index 4f78f1c31..0d161ef66 100644
--- a/docs/source/markdown/podman-exec.1.md.in
+++ b/docs/source/markdown/podman-exec.1.md.in
@@ -1,4 +1,4 @@
-% podman-exec(1)
+% podman-exec 1
## NAME
podman\-exec - Execute a command in a running container
@@ -44,21 +44,7 @@ to run containers such as CRI-O, the last started container could be from either
Pass down to the process N additional file descriptors (in addition to 0, 1, 2). The total FDs will be 3+N.
-#### **--privileged**
-
-Give extended privileges to this container. The default is *false*.
-
-By default, Podman containers are
-"unprivileged" and cannot, for example, modify parts of the operating system.
-This is because by default a container is only allowed limited access to devices.
-A "privileged" container is given the same access to devices as the user launching the container.
-
-A privileged container turns off the security features that isolate the
-container from the host. Dropped Capabilities, limited devices, read/only mount
-points, Apparmor/SELinux separation, and Seccomp filters are all disabled.
-
-Rootless containers cannot have more privileges than the account that launched them.
-
+@@option privileged
#### **--tty**, **-t**