From 2f3cf662b1f97c271335e0777471283c52d4f63d Mon Sep 17 00:00:00 2001 From: Daniel M Barlow Date: Wed, 14 Nov 2018 02:37:41 +0100 Subject: [PATCH] Rename 'Reusing Docker' section (#10885) May make it easier to see the importance of this section --- content/en/docs/setup/minikube.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/setup/minikube.md b/content/en/docs/setup/minikube.md index aa2143e4c3..418c4944b9 100644 --- a/content/en/docs/setup/minikube.md +++ b/content/en/docs/setup/minikube.md @@ -169,7 +169,7 @@ This will use an alternative minikube ISO image containing both rkt, and Docker, See [DRIVERS](https://git.k8s.io/minikube/docs/drivers.md) for details on supported drivers and how to install plugins, if required. -### Reusing the Docker daemon +### Use local images by re-using the Docker daemon When using a single VM of Kubernetes, it's really handy to reuse the Minikube's built-in Docker daemon; as this means you don't have to build a docker registry on your host machine and push the image into it - you can just build inside the same docker daemon as minikube which speeds up local experiments. Just make sure you tag your Docker image with something other than 'latest' and use that tag while you pull the image. Otherwise, if you do not specify version of your image, it will be assumed as `:latest`, with pull image policy of `Always` correspondingly, which may eventually result in `ErrImagePull` as you may not have any versions of your Docker image out there in the default docker registry (usually DockerHub) yet.