From e8ba6c8c1fda75fec9ab3a1175d61140f53b6bd6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Anders=20F=20Bj=C3=B6rklund?= Date: Tue, 13 Aug 2019 21:32:01 +0200 Subject: [PATCH] Fix site documentation links to docker_daemon.md --- site/content/en/docs/Tasks/building.md | 2 +- site/content/en/docs/Tasks/docker_registry.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/site/content/en/docs/Tasks/building.md b/site/content/en/docs/Tasks/building.md index 4194c3ec6270..1da1b954088d 100644 --- a/site/content/en/docs/Tasks/building.md +++ b/site/content/en/docs/Tasks/building.md @@ -10,7 +10,7 @@ When using a single VM of Kubernetes it's really handy to build inside the VM; a ## Docker (containerd) -For Docker, you can either set up your host docker client to communicate by [reusing the docker daemon](docker_daemon.md). +For Docker, you can either set up your host docker client to communicate by [reusing the docker daemon]({{< ref "/docs/tasks/docker_daemon.md" >}}). Or you can use `minikube ssh` to connect to the virtual machine, and run the `docker build` there: diff --git a/site/content/en/docs/Tasks/docker_registry.md b/site/content/en/docs/Tasks/docker_registry.md index a3c08c5ca3b4..64afca1c0000 100644 --- a/site/content/en/docs/Tasks/docker_registry.md +++ b/site/content/en/docs/Tasks/docker_registry.md @@ -7,7 +7,7 @@ description: > How to access the Docker registry within minikube --- -As an alternative to [reusing the Docker daemon](docker_daemon.md), you may enable the registry addon to push images directly into registry. +As an alternative to [reusing the Docker daemon]({{< ref "/docs/tasks/docker_daemon.md" >}}), you may enable the registry addon to push images directly into registry. Steps are as follows: