How To Resolve ErrImagePull Errors

Background

An ErrImagePull error occurs when a container fails to start because it can't find or pull the image specified in the image reference. This error can be caused by issues that include:

• The specified image name is incorrect or is misspelled
• The specified container registry is down or unavailable
• Authentication or authorization to access the image in the container registry failed
• The image is no longer available
• There are network connectivity issues between the Docker host and the registry

Solution

Try the following to resolve ErrImagePull errors:

• Retry the pull: Try pulling the image again; the error may have been transitory.

• Verify the image name and tag: Ensure that the correct image name and tag are specified in the container configuration, including the correct case with any necessary slashes and the correct registry and repository name. The Events section of the describe pod output might contain the following messages if the image name, tag, registry, or repository is the issue:

  • manifest for <name:tag>... not found

  • repository <name> not found: does not exist or no pull access

• Verify image availability: Verify that the specified image exists in the specified repository, that it is up-to-date, and that it can be pulled using the command line or a web browser.

• Check authentication: If the registry that contains the image requires authentication, ensure that you have provided the correct credentials. The Events section of the describe pod output will contain the following message if this is the issue:

  • authorization failed

• Verify network connectivity: Verify that there is a stable network connection between the host and the registry where the image is stored.

• Restart the container runtime: Sometimes a simple restart of the container runtime can resolve the issue.

These are general steps that will frequently resolve an ErrImagePull error; however, the exact solution may vary depending on the specific situation and the cause of the error. If the error still exists after trying these steps, you should check the logs of the container engine or the registry for more specific error messages, and also check system and firewall rule configurations.