From d9ebbbfe5b6a22e61091fe764ae2875aa0bf8064 Mon Sep 17 00:00:00 2001 From: Daniel J Walsh Date: Thu, 7 Jan 2021 05:37:24 -0500 Subject: Switch references of /var/run -> /run Systemd is now complaining or mentioning /var/run as a legacy directory. It has been many years where /var/run is a symlink to /run on all most distributions, make the change to the default. Partial fix for https://github.com/containers/podman/issues/8369 Signed-off-by: Daniel J Walsh --- troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'troubleshooting.md') 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. -- cgit v1.2.3-54-g00ecf