Man pages: refactor common options: --privileged

An easy one. Went with the version from podman-run.

Signed-off-by: Ed Santiago <santiago@redhat.com>

1 files changed, 1 insertions, 15 deletions

diff --git a/docs/source/markdown/podman-create.1.md.in b/docs/source/markdown/podman-create.1.md.in
index 68bd06472..a20aeafcd 100644
--- a/docs/source/markdown/podman-create.1.md.in
+++ b/docs/source/markdown/podman-create.1.md.in
@@ -354,21 +354,7 @@ To make a pod with more granular options, use the `podman pod create` command be
 
 @@option pod-id-file.container
 
-#### **--privileged**
-
-Give extended privileges to this container. The default is *false*.
-
-By default, Podman containers are
-“unprivileged” (=false) and cannot, for example, modify parts of the operating system.
-This is because by default a container is not allowed to access any devices.
-A “privileged” container is given access to all devices.
-
-When the operator executes a privileged container, Podman enables access
-to all devices on the host, turns off graphdriver mount options, as well as
-turning off most of the security measures protecting the host from the
-container.
-
-Rootless containers cannot have more privileges than the account that launched them.
+@@option privileged
 
 #### **--publish**, **-p**=*[[ip:][hostPort]:]containerPort[/protocol]*