<p>I have some images on my local docker instance, one of which is named <code>door_controls</code>:</p>
<pre><code>&gt;docker image ls
REPOSITORY                    TAG       IMAGE ID       CREATED        SIZE
door_controls                 latest    d22f58cdc9c1   3 hours ago    1.12GB
[...]
</code></pre>
<p>This image is also deployed to my minikube instance:</p>
<pre><code>&gt;minikube ssh -- docker image ls
door_controls                             latest    d22f58cdc9c1   3 hours ago     1.12GB
[...]
</code></pre>
<p>(It is also clear to me that these are different docker daemons, because the one on minikube also lists the k8s daemons).
The documentation (and <a href="https://stackoverflow.com/questions/42564058/how-to-use-local-docker-images-with-minikube">this canonical</a> Stackoverflow answer) suggests that</p>
<pre><code>minikube image load door_controls
minikube kubectl run door-controls --image=door_controls --port=7777
</code></pre>
<p>is the way to deploy this image from the command line, but the event log tells me something failed along the way:</p>
<pre><code>Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  59s                default-scheduler  Successfully assigned default/door-controls to minikube
  Normal   Pulling    17s (x3 over 59s)  kubelet            Pulling image &quot;door_controls&quot;
  Warning  Failed     16s (x3 over 57s)  kubelet            Failed to pull image &quot;door_controls&quot;: rpc error: code = Unknown desc = Error response from daemon: pull access denied for door_controls, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
  Warning  Failed     16s (x3 over 57s)  kubelet            Error: ErrImagePull
  Normal   BackOff    1s (x3 over 57s)   kubelet            Back-off pulling image &quot;door_controls&quot;
  Warning  Failed     1s (x3 over 57s)   kubelet            Error: ImagePullBackOff
</code></pre>
<p>In the classic tradition of invoking commands I don't understand in the hope that it fixes the problem, I have followed the advice of another answer and tried setting the docker daemon to minikube's:</p>
<pre><code>&gt;eval $(minikube -p minikube docker-env)
//these aren't echoed by the shell of course
export DOCKER_TLS_VERIFY=&quot;1&quot;
export DOCKER_HOST=&quot;tcp://127.0.0.1:54664&quot;
export DOCKER_CERT_PATH=&quot;/Users/airza/.minikube/certs&quot;
export MINIKUBE_ACTIVE_DOCKERD=&quot;minikube&quot;
</code></pre>
<p>It seems as though the default configuration wants TLS enabled (from localhost to localhost?) but I am not sure how to turn it off or how to add valid TLS from localhost to localhost in the first place.</p>
<p>It is also not clear if this is even the issue or if something else is. Is my nomenclature for the image wrong? Do I need to specify a repo? Why does this image not deploy?</p>

<p>Minikube comes with its own docker daemon and not able to find images by default, the below works in my local env, i noticed the first step is already done and looks like the the image is still being pulled, step-2 might solve the problem below.</p>
<ol>
<li>Set the environment variables with eval $(minikube docker-env), i see you have set this already.</li>
<li>Set ImagePullPolicy to Never in order to use local docker images with the deployment, this will ensure that the image is not pulled from docker repo.</li>
</ol>
<p>you can try running the below yaml on your cluster for your use-case.</p>
<pre><code>apiVersion: v1
kind: Pod
metadata:
  name: test
spec:
  containers:
    image: door_controls
    name: door_controls
    imagePullPolicy: Never
    ports:
      - containerPort: 7777

</code></pre>
<p>blog article: <a href="https://medium.com/bb-tutorials-and-thoughts/how-to-use-own-local-doker-images-with-minikube-2c1ed0b0968" rel="nofollow noreferrer">https://medium.com/bb-tutorials-and-thoughts/how-to-use-own-local-doker-images-with-minikube-2c1ed0b0968</a></p>
