K
Q

How to retry image pull in a kubernetes Pods?

10/26/2016

I am new to kubernetes. I have an issue in the pods. When I run the command

 kubectl get pods

Result:

NAME                   READY     STATUS             RESTARTS   AGE
mysql-apim-db-1viwg    1/1       Running            1          20h
mysql-govdb-qioee      1/1       Running            1          20h
mysql-userdb-l8q8c     1/1       Running            0          20h
wso2am-default-813fy   0/1       ImagePullBackOff   0          20h

Due to an issue of "wso2am-default-813fy" node, I need to restart it. Any suggestion?

-- Dilshani Subasinghe
coreos
docker
kubernetes

Similar Questions

Accessing or Controlling the SRV CNAME in Headless Services
Kubernetes proxy route traffic to different sub services depending on request path
kubernetes nginx ingress // health checks not working
Google Container clusters VS Managed Instance groups

6 Answers

3/30/2019

First try to see what's wrong with the pod:

kubectl logs -p <your_pod>

In my case it was a problem with the YAML file.

So, I needed to correct the configuration file and replace it:

kubectl replace --force -f <yml_file_describing_pod>
-- edubriguenti
Source: StackOverflow
7/12/2017

In case of not having the yaml file:

kubectl get pod PODNAME -n NAMESPACE -o yaml | kubectl replace --force -f -

-- Maciek Sawicki
Source: StackOverflow
10/26/2016

Usually in case of "ImagePullBackOff" it's retried after few seconds/minutes. In case you want to try again manually you can delete the old pod and recreate the pod. The one line command to delete and recreate the pod would be:

kubectl replace --force -f <yml_file_describing_pod>
-- Ayon Nahiyan
Source: StackOverflow
6/1/2017
$ kubectl replace --force -f <resource-file>

if all goes well, you should see something like:

<resource-type> <resource-name> deleted
<resource-type> <resource-name> replaced

details of this can be found in the Kubernetes documentation, "manage-deployment" and kubectl-cheatsheet pages at the time of writing.

-- eversMcc
Source: StackOverflow
8/1/2018

If the Pod is part of a Deployment or Service, deleting it will restart the Pod and, potentially, place it onto another node:

$ kubectl delete po $POD_NAME

replace it if it's an individual Pod:

$ kubectl get po -n $namespace $POD_NAME -o yaml | kubectl replace -f -

-- Carlos Nunez
Source: StackOverflow
8/23/2019

Try with deleting pod it will try to pull image again.

kubectl delete pod <pod_name> -n <namespace_name>

-- Sachin Arote
Source: StackOverflow