Skip to content

Commit

Permalink
Improve doc code formatting
Browse files Browse the repository at this point in the history
Signed-off-by: Ben Bodenmiller <bbodenmiller@gmail.com>
  • Loading branch information
bbodenmiller authored Jun 22, 2022
1 parent ac1d1ad commit e458cf1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/reference/run.md
Original file line number Diff line number Diff line change
Expand Up @@ -1241,15 +1241,15 @@ uid=0(root) gid=0(root) groups=10(wheel),29(audio),99(nogroup),777
| `--cap-add` | Add Linux capabilities |
| `--cap-drop` | Drop Linux capabilities |
| `--privileged` | Give extended privileges to this container |
| `--device=[]` | Allows you to run devices inside the container without the --privileged flag. |
| `--device=[]` | Allows you to run devices inside the container without the `--privileged` flag. |

By default, Docker containers are "unprivileged" and cannot, for
example, run a Docker daemon inside a Docker container. This is because
by default a container is not allowed to access any devices, but a
"privileged" container is given access to all devices (see
the documentation on [cgroups devices](https://www.kernel.org/doc/Documentation/cgroup-v1/devices.txt)).

The --privileged flag gives all capabilities to the container. When the operator
The `--privileged` flag gives all capabilities to the container. When the operator
executes `docker run --privileged`, Docker will enable access to all devices on
the host as well as set some configuration in AppArmor or SELinux to allow the
container nearly all the same access to the host as processes running outside
Expand Down

0 comments on commit e458cf1

Please sign in to comment.