summaryrefslogtreecommitdiff
path: root/troubleshooting.md
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2021-01-07 15:06:17 -0500
committerGitHub <noreply@github.com>2021-01-07 15:06:17 -0500
commit6c132b78f1338c01f60f0fd509710813e2832550 (patch)
tree029911e38ed5dce8ae9fc33651425e1adff485a9 /troubleshooting.md
parent3cf41c4a7349d2f2529ce94801de2de9898ae27f (diff)
parentd9ebbbfe5b6a22e61091fe764ae2875aa0bf8064 (diff)
downloadpodman-6c132b78f1338c01f60f0fd509710813e2832550.tar.gz
podman-6c132b78f1338c01f60f0fd509710813e2832550.tar.bz2
podman-6c132b78f1338c01f60f0fd509710813e2832550.zip
Merge pull request #8771 from rhatdan/run
Switch references of /var/run -> /run
Diffstat (limited to 'troubleshooting.md')
-rw-r--r--troubleshooting.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/troubleshooting.md b/troubleshooting.md
index 78e22fa2f..c028a7714 100644
--- a/troubleshooting.md
+++ b/troubleshooting.md
@@ -344,7 +344,7 @@ After creating a container with Podman's storage directories mounted in from the
When running Podman inside a container, it is recommended to mount at a minimum `/var/lib/containers/storage/` as a volume.
Typically, you will not mount in the host version of the directory, but if you wish to share containers with the host, you can do so.
-If you do mount in the host's `/var/lib/containers/storage`, however, you must also mount in the host's `/var/run/libpod` and `/var/run/containers/storage` directories.
+If you do mount in the host's `/var/lib/containers/storage`, however, you must also mount in the host's `/run/libpod` and `/run/containers/storage` directories.
Not doing this will cause Podman in the container to detect that temporary files have been cleared, leading it to assume a system restart has taken place.
This can cause Podman to reset container states and lose track of running containers.