diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2021-02-03 06:57:23 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-02-03 06:57:23 -0500 |
| commit | a086f601e306e7eac94826d5cc368d6220535074 (patch) | |
| tree | 9e642566c27e6f8ba72e9cb81dd09d121f35606d /docs/tutorials/rootless_tutorial.md | |
| parent | 8f51d325af7a2af76fb4e6664779bda6eb76d12c (diff) | |
| parent | 3d105015f6b56be7f588944c29007603ffe45f62 (diff) | |
| download | podman-a086f601e306e7eac94826d5cc368d6220535074.tar.gz podman-a086f601e306e7eac94826d5cc368d6220535074.tar.bz2 podman-a086f601e306e7eac94826d5cc368d6220535074.zip | |
Merge pull request #9103 from mattcen/patch-1
[CI:DOCS] typo
Diffstat (limited to 'docs/tutorials/rootless_tutorial.md')
| -rw-r--r-- | docs/tutorials/rootless_tutorial.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/tutorials/rootless_tutorial.md b/docs/tutorials/rootless_tutorial.md index cb73fc519..ea5990833 100644 --- a/docs/tutorials/rootless_tutorial.md +++ b/docs/tutorials/rootless_tutorial.md @@ -184,7 +184,7 @@ total 0 We do recognize that this doesn't really match how many people intend to use rootless Podman - they want their UID inside and outside the container to match. Thus, we provide the `--userns=keep-id` flag, which ensures that your user is mapped to its own UID and GID inside the container. -It is also helpful to distinguish between running Podman as a rootless user, and a container which is built to run rootless. If the container you're trying you run has a `USER` which is not root, then when mounting volumes you **must** use `--userns=keep-id`. This is because the container user would not be able to become `root` and access the mounted volumes. +It is also helpful to distinguish between running Podman as a rootless user, and a container which is built to run rootless. If the container you're trying to run has a `USER` which is not root, then when mounting volumes you **must** use `--userns=keep-id`. This is because the container user would not be able to become `root` and access the mounted volumes. Other considerations in regards to volumes: |