Intermittent Error creating pod: container failed to start, ImagePullBackOff

Has anyone ever run into this error with AWX-operator? It just started happening to me today intermittently. I launch my Job Templates and sometimes they fail with this error:

Error creating pod: container failed to start, ImagePullBackOff

I am running AWX-operator on a K3 kubernetes cluster.
On froom k8 dashboard I see this error:

Failed to pull image "": rpc error: code = Unknown desc = failed to pull and unpack image "": failed to resolve reference "": pulling from host failed with status code [manifests latest]: 502 Bad Gateway

Is there something up with


Apologizes for answering my own question and not checking before posting but is having an major outage.



would u mind marking this topic solved

1 Like

Would using something like OpenShift have helped with reliable access to containers?

For AWX not really since we host image on Quay.

Thanks. I understand. Quay did fix the problem pretty quickly, but can you recommend a course of action that could make my AWX more resilient to such outages?

1 Like

Mirroring to a private image registry and deploy using private image registry would probably work.


Also we have the image in as well. This is our staging image registry

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.