summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2021-07-22 14:12:25 -0400
committerGitHub <noreply@github.com>2021-07-22 14:12:25 -0400
commitc522dc2f0920ab4a835577bf09a25bdf9c4fbdbe (patch)
tree428ecc762858a3ee17ca40d9c265a66c885badb1
parent365775489f24bcfe84a7e5257cf64ea51d523b6e (diff)
parent9c659b3bc96435ad4a3e743a99b69d31a8d9fd28 (diff)
downloadpodman-c522dc2f0920ab4a835577bf09a25bdf9c4fbdbe.tar.gz
podman-c522dc2f0920ab4a835577bf09a25bdf9c4fbdbe.tar.bz2
podman-c522dc2f0920ab4a835577bf09a25bdf9c4fbdbe.zip
Merge pull request #11022 from xordspar0/patch-1
[CI:DOCS] Fix broken remote client link
-rw-r--r--troubleshooting.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/troubleshooting.md b/troubleshooting.md
index 575ee16b8..24dcb8e35 100644
--- a/troubleshooting.md
+++ b/troubleshooting.md
@@ -356,7 +356,7 @@ If you do mount in the host's `/var/lib/containers/storage`, however, you must a
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.
-For running containers on the host from inside a container, we also recommend the [Podman remote client](remote_client.md), which only requires a single socket to be mounted into the container.
+For running containers on the host from inside a container, we also recommend the [Podman remote client](docs/tutorials/remote_client.md), which only requires a single socket to be mounted into the container.
### 14) Rootless 'podman build' fails EPERM on NFS: