<p>I tried creating a deployment with minikube cluster connected to virtual box.But it results with below mentioned Imagepullbackoff error(Passed commands on Windows powershell-admin rights)
I tried with docker as a driver but same result.Help me out!!</p>
<p>PS C:\Windows\system32&gt;kubectl get pod
NAME                                  READY   STATUS             RESTARTS   AGE
mongo-express-98c6ff4b4-l7jmn         0/1     ImagePullBackOff   0          116m
mongodb-deployment-67dcfb9c9f-mfvxr   0/1     ImagePullBackOff   0          116m</p>
<pre><code>PS C:\Windows\system32&gt; kubectl describe pod
Name:         mongo-express-98c6ff4b4-l7jmn
Namespace:    default
Priority:     0
Node:         minikube/192.168.59.113
Start Time:   Thu, 30 Jun 2022 19:10:41 +0530
Labels:       app=mongo-express
              pod-template-hash=98c6ff4b4
Annotations:  &lt;none&gt;
Status:       Pending
IP:           172.17.0.4
IPs:
  IP:           172.17.0.4
Controlled By:  ReplicaSet/mongo-express-98c6ff4b4
Containers:
  mongo-express:
    Container ID:
    Image:          mongo-express
    Image ID:
    Port:           8081/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Environment:
      ME_CONFIG_MONGODB_ADMINUSERNAME:  &lt;set to the key 'mongo-root-username' in secret 'mongodb-secret'&gt;  Optional: false
      ME_CONFIG_MONGODB_ADMINPASSWORD:  &lt;set to the key 'mongo-root-password' in secret 'mongodb-secret'&gt;  Optional: false
      ME_CONFIG_MONGODB_SERVER:         &lt;set to the key 'database_url' of config map 'mongodb-configmap'&gt;  Optional: false
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-lp9nk (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  kube-api-access-lp9nk:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       &lt;nil&gt;
    DownwardAPI:             true
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  60m                  default-scheduler  Successfully assigned default/mongo-express-98c6ff4b4-l7jmn to minikube
  Warning  Failed     58m (x6 over 59m)    kubelet            Error: ImagePullBackOff
  Normal   Pulling    58m (x4 over 59m)    kubelet            Pulling image &quot;mongo-express&quot;
  Warning  Failed     58m (x4 over 59m)    kubelet            Failed to pull image &quot;mongo-express&quot;: rpc error: code = Unknown desc = Error response from daemon: Get &quot;https://registry-1.docker.io/v2/&quot;: dial tcp: lookup registry-1.docker.io on 10.0.2.3:53: no such host
  Warning  Failed     58m (x4 over 59m)    kubelet            Error: ErrImagePull
  Warning  Failed     29m (x2 over 36m)    kubelet            Failed to pull image &quot;mongo-express&quot;: rpc error: code = Unknown desc = context deadline exceeded
  Normal   BackOff    19m (x141 over 59m)  kubelet            Back-off pulling image &quot;mongo-express&quot;


Name:         mongodb-deployment-67dcfb9c9f-mfvxr
Namespace:    default
Priority:     0
Node:         minikube/192.168.59.113
Start Time:   Thu, 30 Jun 2022 19:10:32 +0530
Labels:       app=mongodb
              pod-template-hash=67dcfb9c9f
Annotations:  &lt;none&gt;
Status:       Pending
IP:           172.17.0.3
IPs:
  IP:           172.17.0.3
Controlled By:  ReplicaSet/mongodb-deployment-67dcfb9c9f
Containers:
  mongodb:
    Container ID:
    Image:          mongo
    Image ID:
    Port:           27017/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Environment:
      MONGO_INITDB_ROOT_USERNAME:  &lt;set to the key 'mongo-root-username' in secret 'mongodb-secret'&gt;  Optional: false
      MONGO_INITDB_ROOT_PASSWORD:  &lt;set to the key 'mongo-root-password' in secret 'mongodb-secret'&gt;  Optional: false
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ft77v (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  kube-api-access-ft77v:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       &lt;nil&gt;
    DownwardAPI:             true
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  60m                  default-scheduler  Successfully assigned default/mongodb-deployment-67dcfb9c9f-mfvxr to minikube
  Warning  Failed     58m (x6 over 60m)    kubelet            Error: ImagePullBackOff
  Normal   Pulling    58m (x4 over 60m)    kubelet            Pulling image &quot;mongo&quot;
  Warning  Failed     58m (x4 over 60m)    kubelet            Failed to pull image &quot;mongo&quot;: rpc error: code = Unknown desc = Error response from daemon: Get &quot;https://registry-1.docker.io/v2/&quot;: dial tcp: lookup registry-1.docker.io on 10.0.2.3:53: no such host
  Warning  Failed     58m (x4 over 60m)    kubelet            Error: ErrImagePull
  Warning  Failed     34m                  kubelet            Failed to pull image &quot;mongo&quot;: rpc error: code = Unknown desc = context deadline exceeded
  Normal   BackOff    19m (x134 over 60m)  kubelet            Back-off pulling image &quot;mongo&quot;
</code></pre>

Vj_raghav
<p>Try to pull image first, then create deployment.</p>
<pre><code>minikube image pull mongo
</code></pre>
<p><strong>UPD</strong>: Sometimes even <code>image pull</code> doesn't help. minikube developers said that you can curl to check whether you can connect to repo or not. There also may be ISP issues. Temporary changing my ISP to mobile data and installing needed pods worked for me.</p>
