diff options
author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2020-01-30 06:40:16 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-01-30 06:40:16 -0800 |
commit | 1729350f6636b18a0555484d1ece307b9d2fd828 (patch) | |
tree | ad1064a40e29ead3129ba1c500751133fb845a17 /docs | |
parent | e83e9f5d7194b43365e288f53dcd2114bdf9fa91 (diff) | |
parent | 103b5e7807fbbe2cdee0d7bfbc8c253e78700d87 (diff) | |
download | podman-1729350f6636b18a0555484d1ece307b9d2fd828.tar.gz podman-1729350f6636b18a0555484d1ece307b9d2fd828.tar.bz2 podman-1729350f6636b18a0555484d1ece307b9d2fd828.zip |
Merge pull request #4951 from rpjday/docs/unshare
markdown: fix grammar/formatting, standardize on markdown
Diffstat (limited to 'docs')
-rw-r--r-- | docs/source/markdown/podman-unshare.1.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/source/markdown/podman-unshare.1.md b/docs/source/markdown/podman-unshare.1.md index 9052b97ab..f2eb02814 100644 --- a/docs/source/markdown/podman-unshare.1.md +++ b/docs/source/markdown/podman-unshare.1.md @@ -10,19 +10,19 @@ podman\-unshare - Run a command inside of a modified user namespace Launches a process (by default, *$SHELL*) in a new user namespace. The user namespace is configured so that the invoking user's UID and primary GID appear to be UID 0 and GID 0, respectively. Any ranges which match that user and -group in /etc/subuid and /etc/subgid are also mapped in as themselves with the +group in `/etc/subuid` and `/etc/subgid` are also mapped in as themselves with the help of the *newuidmap(1)* and *newgidmap(1)* helpers. -podman unshare is useful for troubleshooting unprivileged operations and for +**podman unshare** is useful for troubleshooting unprivileged operations and for manually clearing storage and other data related to images and containers. -It is also useful if you want to use the `podman mount` command. If an unprivileged users wants to mount and work with a container, then they need to execute -podman unshare. Executing `podman mount` fails for unprivileged users unless the user is running inside a `podman unshare` session. +It is also useful if you want to use the **podman mount** command. If an unprivileged user wants to mount and work with a container, then they need to execute +**podman unshare**. Executing **podman mount** fails for unprivileged users unless the user is running inside a **podman unshare** session. The unshare session defines two environment variables: -**CONTAINERS_GRAPHROOT** the path to the persistent containers data. -**CONTAINERS_RUNROOT** the path to the volatile containers data. +- **CONTAINERS_GRAPHROOT**: the path to the persistent container's data. +- **CONTAINERS_RUNROOT**: the path to the volatile container's data. ## EXAMPLE |