<p>I am really confused, I had being learning kubernetes with minikube creating services and other things.</p>

<p>The problem comes in the following shape:</p>

<p>I run the following commands after a fresh install of minikube:</p>

<p><code>eval $(minikube docker-env)</code> </p>

<p>The reason is because I want to get an image from my computer to be used with minikube. My understanding is that with this command I am in the same context for minikube and docker, so I can access my local images. "Please correct me if I am wrong here".</p>

<p><code>minikube start</code></p>

<p>So I get up and running the cluster, and ready to start creating things.</p>

<p>I want to pull the following container:</p>

<p><code>docker pull nginx/nginx-ingress</code> </p>

<p>Because I want to try an ingress controller to work with my services.</p>

<p>But then I get this weird message:</p>

<p><code>Using default tag: latest
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at tcp://192.168.99.101:2376. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at tcp://192.168.99.101:2376. Is the docker daemon running?
</code></p>

<p>I run:</p>

<p><code>docker ps</code></p>

<p>And no results with a hang out.</p>

<p>I go to another terminal, I run the <code>docker ps</code> and it works like a charm.</p>

<p>Please if someone can bring some light to me of the impact of the command:</p>

<p><code>eval $(minikube docker-env)</code></p>

<p>And if you know why in my current Term with minikube running cannot access to my docker machine would help a lot.</p>

juan garcia
<p><code>minikube</code> starts a dedicated virtual machine as a single-node Kubernetes cluster.  If you have other Docker environments (a separate Docker Machine VM, the Docker Toolbox VM, the Docker for Mac or Docker for Windows environments, or a Linux-native Docker) these are separate from the Docker in the VM.  You can't share images or containers between these environments.</p>

<p>If you have private images that aren't published to a registry, you'll have to re-<code>docker build</code> them when you switch to the Minikube environment.  You otherwise don't specifically have to <code>docker pull</code> things that you're using, when you reference them in a Kubernetes pod spec Kubernetes will pull them for you.</p>
