2019-03-10 19:02:52 +00:00
# Reusing the Docker daemon
2017-05-03 21:53:51 +00:00
2018-03-24 03:07:41 +00:00
When using a single VM of Kubernetes it's 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.
2017-05-03 21:53:51 +00:00
2017-07-27 06:03:23 +00:00
To be able to work with the docker daemon on your mac/linux host use the docker-env command in your shell:
2017-05-03 21:53:51 +00:00
2018-02-12 11:42:03 +00:00
```shell
2017-05-03 21:53:51 +00:00
eval $(minikube docker-env)
```
2019-03-10 19:02:52 +00:00
2018-03-24 03:07:41 +00:00
You should now be able to use docker on the command line on your host mac/linux machine talking to the docker daemon inside the minikube VM:
2019-03-10 19:02:52 +00:00
2018-02-12 11:42:03 +00:00
```shell
2017-05-03 21:53:51 +00:00
docker ps
```
On Centos 7, docker may report the following error:
2018-02-12 11:42:03 +00:00
```shell
2017-05-03 21:53:51 +00:00
Could not read CA certificate "/etc/docker/ca.pem": open /etc/docker/ca.pem: no such file or directory
```
The fix is to update /etc/sysconfig/docker to ensure that minikube's environment changes are respected:
2018-02-12 11:42:03 +00:00
```diff
2017-05-03 21:53:51 +00:00
< DOCKER_CERT_PATH = / etc / docker
---
> if [ -z "${DOCKER_CERT_PATH}" ]; then
> DOCKER_CERT_PATH=/etc/docker
> fi
```
2017-06-16 12:26:51 +00:00
Remember to turn off the _imagePullPolicy:Always_ , as otherwise Kubernetes won't use images you built locally.