<p>When I try to run a container in the cluster, I get a message "<code>deployment test created</code>" but when I look at the dashboard I can see that its in an error state (<code>Failed to pull image...</code>, it was not able to pull the image from the local minikube docker env due to authorization issues</p>

<p>My steps were:</p>

<ol>
<li>Start minikube using hyperv and setting the <code>--insecure-registry</code> switch to 10.0.0.0/8, also tried 0.0.0.0/0 - Kubernetes version 1.9.0 also tried 1.8.0</li>
<li>Set the <code>docker env</code> to the minikube docker via <code>minikube docker-env | Invoke-Expression</code></li>
<li>build docker image - image builds and exists in minikube local docker</li>
<li><code>kubectl run test --image test-service --port 1101</code></li>
</ol>

<p>This is the result:</p>

<p><a href="https://i.stack.imgur.com/IsEXO.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/IsEXO.jpg" alt="Failed Deployment"></a></p>

<p>What am I missing?</p>

<p>As discussed in the comments, <code>openfaas/faas-netes</code> issue 135 illustrates a similar issue, and mention as a possible solution:</p>

<blockquote>
  <p><code>imagePullPolicy</code> if not mentioned should have defaulted to <code>Never</code> instead of <code>Always</code>.</p>
</blockquote>

<p>The <a href="https://stackoverflow.com/users/10387/tim-jarvis">OP Tim Jarvis</a> realized then:</p>

<blockquote>
  <p>I realized it was not an auth issue, but that it was always wanting to pull from an external repo.<br>
  The fix for me was to use the <code>imagePullPolicy</code> of <code>IfNotPresent</code>.</p>
</blockquote>
