Comment on page
ImagePullBackoff error
How to debug an ImagePullBackOff error
An ImagePullBackOff error means that an instance could not start because the image to build that instance could not be pulled from the image registry.
This is often a temporary error, so restarting the instance will be attempted. After each unsuccessful start, the delay before the next attempt to restart is increased.
An ImagePullBackOff error is usually the result of one of the following issues:
The build failed
Try to kick off a new build. You can trigger a new build by clicking Apply under "Apply Latest Configuration" in the Settings tab.
The Docker Hub integration failed
If you're pulling images from Docker Hub, you might not have set your credentials for Docker Hub. Make sure you've followed the correct steps to integrate Release with DockerHub.
There is a typing error in the service definition
Double-check your service definitions. A typing error or incorrect name can cause an ImagePullBackOff error if the specified image does not exist.
A network glitch
This is rare, but it can happen. Try again after some time and the problem may resolve itself.
Using underscores in the Release YAML file
Use dashes instead of underscores in your Release YAML file.
Last modified 4mo ago