# Stork-scheduler pods don't come up because of ImagePullBackoff error

**URL:** <https://forums.portworx.com/t/stork-scheduler-pods-dont-come-up-because-of-imagepullbackoff-error/1487>\
**Category:** Portworx Install\
**Created:** [November 10, 2022, 10:40am UTC](https://forums.portworx.com/t/stork-scheduler-pods-dont-come-up-because-of-imagepullbackoff-error/1487 "2022-11-10T10:40:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![etake](https://avatars.discourse-cdn.com/v4/letter/e/838e76/32.png) [@etake](https://forums.portworx.com/u/etake)\
**Post date:** [November 10, 2022, 10:40am UTC](https://forums.portworx.com/t/stork-scheduler-pods-dont-come-up-because-of-imagepullbackoff-error/1487/1 "2022-11-10T10:40:48Z")

</div>

## Hello. I’ve just installed Portworx 2.9.1.3 (for CP4D) on our internal Baremetal OCP4.10 cluster with the file “CP4D\_ENT\_ED\_Portworx\_2.9.1.3.tgz”. “pxctl status” command says that it’s operational,but all of stork scheduler pods fail to start up due to “ImagePullBackoff” error as below:

[root@ilab081062 work]# oc get pod  
NAME READY STATUS RESTARTS AGE  
portworx-api-d6bsm 1/1 Running 0 49m  
portworx-api-s9hg2 1/1 Running 0 49m  
portworx-api-z4wnl 1/1 Running 0 49m  
portworx-kvdb-66rlr 1/1 Running 0 45m  
portworx-kvdb-hxntf 1/1 Running 0 45m  
portworx-kvdb-w6bvv 1/1 Running 0 45m  
portworx-operator-69b78b9cdd-cn56b 1/1 Running 0 54m  
px-csi-ext-69b86bbc99-5pt85 3/3 Running 0 49m  
px-csi-ext-69b86bbc99-t5gtk 3/3 Running 0 49m  
px-csi-ext-69b86bbc99-v2dhw 3/3 Running 0 49m  
px-storage-cluster-646p2 2/2 Running 0 49m  
px-storage-cluster-8scp4 2/2 Running 0 49m  
px-storage-cluster-ssxct 2/2 Running 0 49m  
stork-65b574fb9b-4crwq 1/1 Running 0 49m  
stork-65b574fb9b-5cpfl 1/1 Running 0 49m  
stork-65b574fb9b-s5zbr 1/1 Running 0 49m  
stork-scheduler-7c9c9d99bf-j74m7 0/1 ImagePullBackOff 0 49m  
stork-scheduler-7c9c9d99bf-ppmgm 0/1 ImagePullBackOff 0 44m  
stork-scheduler-7c9c9d99bf-x8zhh 0/1 ImagePullBackOff 0 49m

* * *

The result of “oc describe pod” command shows that it’s requesting the image “kube-scheduler-amd64:v1.21.4”, but the zip file doesn’t contain the image (instead kube-scheduler-amd64:v1.21.1 is included in it).  
How can I get v1.21.4 image?

Warning Failed 18m (x4 over 20m) kubelet Failed to pull image “[ilab081062.lab.japan.ibm.com:5000/kube-system/kube-scheduler-amd64:v1.21.4](http://ilab081062.lab.japan.ibm.com:5000/kube-system/kube-scheduler-amd64:v1.21.4)”: rpc error: code = Unknown desc = reading manifest v1.21.4 in [ilab081062.lab.japan.ibm.com:5000/kube-system/kube-scheduler-amd64:](http://ilab081062.lab.japan.ibm.com:5000/kube-system/kube-scheduler-amd64:) manifest unknown: manifest unknown

---

<div class="post-metadata">

**Author:** ![etake](https://avatars.discourse-cdn.com/v4/letter/e/838e76/32.png) [@etake](https://forums.portworx.com/u/etake)\
**Post date:** [November 10, 2022, 11:02am UTC](https://forums.portworx.com/t/stork-scheduler-pods-dont-come-up-because-of-imagepullbackoff-error/1487/2 "2022-11-10T11:02:40Z")

</div>

Hello. I succeeded downloading “stork-scheduler v1.21.4” image and pushed it to our private registry.  
However it doesn’t seem to work with the other images and all the new pods failed due to “CreatingContainerError”.  
So I editted “stork-scheduler” deployment definition and replaced the image tag with “v1.21.1” that is included in the installation zip file.  
One of the three pods started running, but since it is controlled by its operator pod, the definition was updated just after that and the other pods failed to start up.  
How can we change the image tag used by portworx?