Skip to content

Commit

Permalink
Rename 'Reusing Docker' section (#10885)
Browse files Browse the repository at this point in the history
May make it easier to see the importance of this section
  • Loading branch information
danielmbarlow authored and k8s-ci-robot committed Nov 14, 2018
1 parent 76c65a8 commit 2f3cf66
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/en/docs/setup/minikube.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down

0 comments on commit 2f3cf66

Please sign in to comment.