What is the meaning of ImagePullBackOff status on a Kubernetes pod?

前端 未结 9 1469
梦毁少年i
梦毁少年i 2021-02-02 04:49

I\'m trying to run my first kubernetes pod locally. I\'ve run the following command (from here):

export ARCH=amd64
docker run -d \\
    --volume=/:/rootfs:ro \\
         


        
9条回答
  •  清歌不尽
    2021-02-02 05:29

    Despite all the other great answers none helped me until I found a comment that pointed out this Updating images:

    The default pull policy is IfNotPresent which causes the kubelet to skip pulling an image if it already exists.

    That's exactly what I wanted, but didn't seem to work.

    Reading further said the following:

    If you would like to always force a pull, you can do one of the following:

    • omit the imagePullPolicy and use :latest as the tag for the image to use.

    When I replaced latest with a version (that I had pushed to minikube's Docker daemon), it worked fine.

    $ kubectl create deployment presto-coordinator \
        --image=warsaw-data-meetup/presto-coordinator:beta0
    deployment.apps/presto-coordinator created
    
    $ kubectl get deployments
    NAME                 READY   UP-TO-DATE   AVAILABLE   AGE
    presto-coordinator   1/1     1            1           3s
    

    Find the pod of the deployment (using kubectl get pods) and use kubectl describe pod to find out more on the pod.

提交回复
热议问题