diff options
| -rw-r--r-- | .cirrus.yml | 5 | ||||
| -rw-r--r-- | docs/source/markdown/podman-unshare.1.md | 12 |
2 files changed, 11 insertions, 6 deletions
diff --git a/.cirrus.yml b/.cirrus.yml index e1810fab6..bb2da0812 100644 --- a/.cirrus.yml +++ b/.cirrus.yml @@ -85,10 +85,15 @@ gce_instance: # quick format, lint, and unit tests on the standard platform. gating_task: + # Only run this on PRs, never during post-merge testing. This is also required + # for proper setting of EPOCH_TEST_COMMIT value, required by validation tools. + only_if: $CIRRUS_BRANCH != $DEST_BRANCH + env: CIRRUS_WORKING_DIR: "/usr/src/libpod" GOPATH: "/go" GOSRC: "/go/src/github.com/containers/libpod" + EPOCH_TEST_COMMIT: "${CIRRUS_BASE_SHA}" # Runs within Cirrus's "community cluster" container: 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 |