Error creating pod: container failed to start, ImagePullBackOff

Archives AWX Project
1

I am using AWX20.0.0

It worked fine for up to 2 months

“Error creating pod: container failed to start, ImagePullBackOff” is displayed in Job Output View when the playbook is executed.

I want to know the cause. Does anyone have similar symptoms?

2

Are you using the default awx-ee image to run these jobs?

3

If you are not using a default execution environment image, you may need to configure an image pull secret if the registry is private/protected. Please note that the “image_pull_secrets” field on the spec is plural and takes an array, not a string. https://github.com/ansible/awx-operator#deploying-a-specific-version-of-awx

Thanks,
AWX Team

4

Are you using the default awx-ee image to run these jobs?
Yes. However, it seems that the environment changed while I was away from the team.
Originally, when it was built, it communicated with the Internet.

The company policy has become stricter and we are currently removing the proxy setting.
Now the environment cannot connect to the internet. ’

When I executed the command “minikube logs”, the following message was output.

5

Hi, it’s possible to deploy without internet, see this discussion https://groups.google.com/g/awx-project/c/e_amqVXwROE

You will need to set up a private registry to host all of the images that will be referenced by AWX

Let us know if that is helpful

AWX Team