<p><strong>Cannot pull image from local docker insecured registry repository inside Minikube.</strong><br><br>
I'm running Docker-toolbox v1.12.2 using Linux VM (Upstart) installed on Oracle VirtualBox 5.1.6 under Windows 7.<br></p>

<p>I've created a docker image and push (tag and then push) it into a local insecured docker-registry v2 that running on 192.168.99.100:5000/image/name.<br>
<code>docker run -d -p 5000:5000 --restart=always --name registry registry:2</code><br>
and inside the VM, on /var/lib/boot2docker/profile I've add to the EXTRA_ARGS the flag <br><code>--insecure-registry 192.168.99.100:5000</code> .</p>

<p><code>docker push</code> &amp; <code>docker pull</code> from <code>localhost:5000/image/name</code> are working fine within Docker(VM).<br> <br>
_catalog is reachable from Postman :<code>GET http:192.168.99.100:5000/v2/_catalog</code> and I'm able to get the images inside the registry.</p>

<p>I'm starting my Minikube v0.15.0 VM with the command:<br></p>

<p><code>minikube start --insecure-registry=192.168.99.100:5000</code></p>

<p><strong>I'm under company PROXY</strong> so I've added the proxy in the command line (CMD):<br>
<code>set HTTP/HTTPS_PROXY=my.company.proxy:8080</code> and <code>set NO_PROXY={minikube ip}</code>.<br>
Then Kubernetes dashboard started to work for me.</p>

<p>Now for the real problem, when running the command:<br>
<code>kubectl run image-name --image=192.168.99.100:5000/image/name --port=9999</code>
to pull image from my local docker registry into Kubernetes its saying</p>

<blockquote>
  <p>deployment "image-name" created</p>
</blockquote>

<p>But inside Kubernetes > Deployments I'm getting the following error:</p>

<blockquote>
  <p>Failed to pull image "192.168.99.109:5000/image/name": image pull failed for 192.168.99.100:5000/image/name:latest, this may be because there are no credentials on this request. details: (Error response from daemon: Get <a href="https://192.168.99.100:5000/v1/_ping" rel="nofollow noreferrer">https://192.168.99.100:5000/v1/_ping</a>: Tunnel or SSL Forbidden)</p>
</blockquote>

<p>Can anyone help here with that <strong>Tunnel or SSL Forbidden error</strong>, it's driving me crazy, and I've tried so many solutions to configure --insecrue-registery inside docker, inside Kubernetes or when running the dokcer-registry.</p>

<p>BTW why it's refering to v1/_ping? i'm using the docker registry v2.</p>

<p>Seems like minikube cannot see the same network that your registry is running. Can you try running <code>minikube ssh</code> then run your curl for the catalog? </p>

<p>Also, as an alternative, you could run <code>eval(minikube docker-env)</code> which then will set your local docker client to use the docker server inside minikube. </p>

<p>So for example if you built an image tagged with <code>myimage/foo</code> it would build and put that image on the minikube docker host, so when you deployed the image, it wouldn't need to be pulled. </p>
