<blockquote>
<p>Failed to pull image &quot;/posts:0.0.1&quot;: rpc error: code =
Unknown desc = Error response from daemon: pull access denied for
/posts, repository does not exist or may require 'docker
login': denied: requested access to the resource is denied</p>
</blockquote>
<p><strong>Debian 10, minikube and kubectl installed and docker.
if i run docker with this image - all is fine.</strong></p>
<blockquote>
<p>pavel@debian:~$ kubectl version Client Version:
version.Info{Major:&quot;1&quot;, Minor:&quot;19&quot;, GitVersion:&quot;v1.19.4&quot;,
GitCommit:&quot;123&quot;,
GitTreeState:&quot;clean&quot;, BuildDate:&quot;2020-11-11T13:17:17Z&quot;,
GoVersion:&quot;go1.15.2&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;} Server
Version: version.Info{Major:&quot;1&quot;, Minor:&quot;19&quot;, GitVersion:&quot;v1.19.4&quot;,
GitCommit:&quot;123&quot;,
GitTreeState:&quot;clean&quot;, BuildDate:&quot;2020-11-11T13:09:17Z&quot;,
GoVersion:&quot;go1.15.2&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}</p>
</blockquote>
<p>posts.yaml</p>
<pre><code>apiVersion: v1
kind: Pod
metadata:
  name: posts
spec:
  containers:
    - name: posts
      image: &lt;mylogin&gt;/posts:0.0.1
</code></pre>
<p><strong>kubectl apply -f posts.yaml</strong></p>
<p><strong>debian:~$ kubectl describe pod posts</strong></p>
<pre><code>Name:         posts
Namespace:    default
Priority:     0
Node:         minikube/192.168.49.2
Start Time:   Wed, 25 Nov 2020 07:06:47 +0400
Labels:       &lt;none&gt;
Annotations:  &lt;none&gt;
Status:       Pending
IP:           172.17.0.4
IPs:
  IP:  172.17.0.4
Containers:
  posts:
    Container ID:   
    Image:          &lt;mylogin&gt;/posts:0.0.1
    Image ID:       
    Port:           &lt;none&gt;
    Host Port:      &lt;none&gt;
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Environment:    &lt;none&gt;
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-b9gkg (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-b9gkg:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-b9gkg
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  &lt;none&gt;
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  23m                   default-scheduler  Successfully assigned default/posts to minikube
  Normal   Pulling    21m (x4 over 23m)     kubelet            Pulling image &quot;&lt;mylogin&gt;/posts:0.0.1&quot;
  Warning  Failed     21m (x4 over 23m)     kubelet            Failed to pull image &quot;&lt;mylogin&gt;/posts:0.0.1&quot;: rpc error: code = Unknown desc = Error response from daemon: pull access denied for &lt;mylogin&gt;/posts, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
  Warning  Failed     21m (x4 over 23m)     kubelet            Error: ErrImagePull
  Warning  Failed     7m53s (x63 over 23m)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    2m58s (x84 over 23m)  kubelet            Back-off pulling image &quot;&lt;mylogin&gt;/posts:0.0.1&quot;
</code></pre>

<p>Minikube is unable to directly access your local docker repository. There are several methods to resolve this and they are elaborated upon here: <a href="https://minikube.sigs.k8s.io/docs/handbook/pushing/" rel="noreferrer">https://minikube.sigs.k8s.io/docs/handbook/pushing/</a></p>
<p>Personally, I simply added the image to the Minikube cache using <code>minikube cache add &lt;image tag&gt;</code> and you need to change the <code>imagePullPolicy</code> inside your yaml file to Never. This way, it will default to using the local image you cached into your minikube. You can reload your cache as well after adding it in. This is probably the simplest way if you use Docker to test the containers before adding them to the cluster.</p>
<p>You can give the other methods a try as well including using the daemon inside Minikube to build the container image directly.</p>
