Skip to content

Commit

Permalink
Merge pull request kubernetes#1995 from king-julien/master
Browse files Browse the repository at this point in the history
More Description: use the minikube's built-in Docker daemon
  • Loading branch information
devin-donnelly authored Dec 22, 2016
2 parents 51d3c31 + 5e1bd59 commit e43373e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/getting-started-guides/minikube.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ plugins, if required.

### Reusing the Docker daemon

When using a single VM of kubernetes its really handy to reuse the Docker daemon inside the VM; as this means you don't have to build on your host machine and push the image into a docker registry - you can just build inside the same docker daemon as minikube which speeds up local experiments.
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.

To be able to work with the docker daemon on your mac/linux host use the [docker-env command](./docs/minikube_docker-env.md) in your shell:

Expand Down

0 comments on commit e43373e

Please sign in to comment.