summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJordan Christiansen <xordspar0@gmail.com>2021-07-22 08:43:47 -0500
committerJordan Christiansen <jordan.christiansen@target.com>2021-07-22 08:48:11 -0500
commit9c659b3bc96435ad4a3e743a99b69d31a8d9fd28 (patch)
tree9722f6e4aa3aa57a3dc57b8bc5ca124d0d9fca57
parent6370622444676db812cbc54aef56e691ea7788d0 (diff)
downloadpodman-9c659b3bc96435ad4a3e743a99b69d31a8d9fd28.tar.gz
podman-9c659b3bc96435ad4a3e743a99b69d31a8d9fd28.tar.bz2
podman-9c659b3bc96435ad4a3e743a99b69d31a8d9fd28.zip
docs: fix broken remote client link
Signed-off-by: Jordan Christiansen <jordan.christiansen@target.com>
-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: