summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorGiuseppe Scrivano <gscrivan@redhat.com>2019-05-16 16:31:08 +0200
committerGiuseppe Scrivano <gscrivan@redhat.com>2019-05-16 16:31:21 +0200
commit8b344065d2b9cc8c98b7b841d5d6845aca2f0ac3 (patch)
treed57fcce168591327a37500c3cc13a3e0bc9294f5 /docs
parent4b480240573be4cd8fe04505b6a435a6aa454f86 (diff)
downloadpodman-8b344065d2b9cc8c98b7b841d5d6845aca2f0ac3.tar.gz
podman-8b344065d2b9cc8c98b7b841d5d6845aca2f0ac3.tar.bz2
podman-8b344065d2b9cc8c98b7b841d5d6845aca2f0ac3.zip
unshare: define CONTAINERS_GRAPHROOT and CONTAINERS_RUNROOT
define two environment variables, that simplify the task of cleaning up the storage, as we can do something like: podman unshare sh -c 'rm -rf $CONTAINERS_GRAPHROOT $CONTAINERS_RUNROOT' Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/podman-unshare.1.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/docs/podman-unshare.1.md b/docs/podman-unshare.1.md
index a7f018ce1..a10fb40f9 100644
--- a/docs/podman-unshare.1.md
+++ b/docs/podman-unshare.1.md
@@ -19,6 +19,11 @@ 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.
+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.
+
## EXAMPLE
```
@@ -34,4 +39,4 @@ $ podman unshare cat /proc/self/uid_map /proc/self/gid_map
## SEE ALSO
-podman(1), podman-mount(1), namespaces(7), newuidmap(1), newgidmap(1), user\_namespaces(7) \ No newline at end of file
+podman(1), podman-mount(1), namespaces(7), newuidmap(1), newgidmap(1), user\_namespaces(7)