whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename 'Reusing Docker' section (#10885)

Browse Source 
May make it easier to see the importance of this section
This commit is contained in:
Daniel M Barlow
2018-11-14 02:37:41 +01:00
committed by k8s-ci-robot
parent 76c65a8418
commit 2f3cf662b1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/minikube.md
+1 -1
View File
@@ -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.