<p>I have a private Docker image registry running on a Linux VM (10.78.0.228:5000) and a Kubernetes master running on a different VM running Centos Linux 7.</p>

<p>I used the below command to create a POD:<br>
<code>kubectl create --insecure-skip-tls-verify -f monitorms-rc.yml</code></p>

<p>I get this:</p>

<blockquote>
  <p>sample   monitorms-mmqhm    0/1    ImagePullBackOff   0  8m</p>
</blockquote>

<p>and upon running:
<code>kubectl describe pod monitorms-mmqhm --namespace=sample</code></p>

<blockquote>
  <p>Warning Failed Failed to pull image "10.78.0.228:5000/monitorms":
  Error response from daemon: {"message":"Get
  <a href="https://10.78.0.228:5000/v1/_ping" rel="noreferrer">https://10.78.0.228:5000/v1/_ping</a>: x509: certificate signed by unknown
  authority"}</p>
</blockquote>

<p>Isn't Kubernetes supposed to ignore the server certificate for all operations during POD creation when the <code>--insecure-skip-tls-verify</code> is passed?</p>

<p>If not, how do I make it ignore the tls verification while pulling the docker image?</p>

<p><strong>PS:</strong></p>

<p><strong>Kubernetes version :</strong></p>

<p>Client Version: <code>v1.5.2</code>
Server Version: <code>v1.5.2</code></p>

<p>I have raised this issue here: <a href="https://github.com/kubernetes/kubernetes/issues/43924" rel="noreferrer">https://github.com/kubernetes/kubernetes/issues/43924</a></p>

Rushil Paul
<p>The issue you're seeing is actually a docker issue. Using <code>--insecure-skip-tls-verify</code> is a valid arg to <code>kubectl</code>, but it only deals with the connecition between <code>kubectl</code> and the kubernetes API server. The error you're seeing is actually because the docker daemon cannot login to the private registry because the cert it's using in unsigned.</p>

<p>Have a look at the <a href="https://docs.docker.com/registry/insecure/" rel="noreferrer">Docker insecure registry docs</a> and this should solve your problem.</p>
