title: Kind (Kubernetes) cluster throwing ImagePullBackOff error
body: <p>I need to pull the image from public docker repository i.e <strong>hello-world:latest</strong> and run that image on kubernetes. I created cluster using <strong>Kind</strong> . I ran that image using the below command</p>
  <pre><code>kubectl run test-pod --image=hello-world
  </code></pre>
  <p>Then I did</p>
  <pre><code>kubectl describe pods 
  </code></pre>
  <p>to get the status of the pods. It threw me <strong>ImagePullBackOff</strong> error . Please find the snapshot below. It seems there is some network issue when pulling the image using kind cluster. Although I am able to pull image from <strong>docker</strong> easily .</p>
  <p><a href="https://i.stack.imgur.com/7dXYu.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/7dXYu.png" alt="enter image description here" /></a></p>
  <p>Have searched the whole internet regarding this issue but nothing worked out. Following is my pod specification :</p>
  <p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
  <div class="snippet-code">
  <pre class="snippet-code-html lang-html prettyprint-override"><code>apiVersion: v1
  kind: Pod
  metadata:
    creationTimestamp: "2022-05-16T15:01:17Z"
    labels:
      run: test-pod
    name: test-pod
    namespace: default
    resourceVersion: "4370"
    uid: 6ef121e2-805b-4022-9a13-c17c031aea88
  spec:
    containers:
    - image: hello-world
      imagePullPolicy: Always
      name: test-pod
      resources: {}
      terminationMessagePath: /dev/termination-log
      terminationMessagePolicy: File
      volumeMounts:
      - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
        name: kube-api-access-jjsmp
        readOnly: true
    dnsPolicy: ClusterFirst
    enableServiceLinks: true
    nodeName: kind-control-plane
    preemptionPolicy: PreemptLowerPriority
    priority: 0
    restartPolicy: Always
    schedulerName: default-scheduler
    securityContext: {}
    serviceAccount: default
    serviceAccountName: default
    terminationGracePeriodSeconds: 30
    tolerations:
    - effect: NoExecute
      key: node.kubernetes.io/not-ready
      operator: Exists
      tolerationSeconds: 300
    - effect: NoExecute
      key: node.kubernetes.io/unreachable
      operator: Exists
      tolerationSeconds: 300
    volumes:
    - name: kube-api-access-jjsmp
      projected:
        defaultMode: 420
        sources:
        - serviceAccountToken:
            expirationSeconds: 3607
            path: token
        - configMap:
            items:
            - key: ca.crt
              path: ca.crt
            name: kube-root-ca.crt
        - downwardAPI:
            items:
            - fieldRef:
                apiVersion: v1
                fieldPath: metadata.namespace
              path: namespace
  status:
    conditions:
    - lastProbeTime: null
      lastTransitionTime: "2022-05-16T15:01:17Z"
      status: "True"
      type: Initialized
    - lastProbeTime: null
      lastTransitionTime: "2022-05-16T15:01:17Z"
      message: 'containers with unready status: [test-pod]'
      reason: ContainersNotReady
      status: "False"
      type: Ready
  containerStatuses:
    - image: hello-world
      imageID: ""
      lastState: {}
      name: test-pod
      ready: false
      restartCount: 0
      started: false
      state:
        waiting:
          message: Back-off pulling image "hello-world"
          reason: ImagePullBackOff
    hostIP: 172.18.0.2
    phase: Pending
    podIP: 10.244.0.5
    podIPs:
    - ip: 10.244.0.5
    qosClass: BestEffort
    startTime: "2022-05-16T15:01:17Z"</code></pre>
  </div>
  </div>
  </p>