Podman pull fails with reported 503 "Service Unavailable" error

Solution Verified - Updated -

Issue

When pulling images, either directly or through a container platform, the pull fails with a 503 "Service Unavailable" error:

# podman pull quay.io/openshift-release-dev/ocp-release@sha256:039a4ef7c128a049ccf916a1d68ce93e8f5494b44d5a75df60c85e9e7191dacc --authfile pull-secret-5.json
Trying to pull quay.io/openshift-release-dev/ocp-release@sha256:039a4ef7c128a049ccf916a1d68ce93e8f5494b44d5a75df60c85e9e7191dacc...Getting image source signatures
Copying blob cf5693de4d3c done
Copying blob 1b608614ec70 done
Copying blob 0bdf97977791 done
Copying blob de790f475ddb done
Copying blob 8b8c7ad8f3fb done
ERRO[0141] Error pulling image ref //quay.io/openshift-release-dev/ocp-release@sha256:039a4ef7c128a049ccf916a1d68ce93e8f5494b44d5a75df60c85e9e7191dacc: Error reading blob sha256:23302e52b49d49a0a25da8ea870bc1973e7d51c9b306f3539cd397318bd8b0a5: Invalid status code returned when fetching blob 503 (Service Unavailable)
Failed
Error: error pulling image "quay.io/openshift-release-dev/ocp-release@sha256:039a4ef7c128a049ccf916a1d68ce93e8f5494b44d5a75df60c85e9e7191dacc": unable to pull quay.io/openshift-release-dev/ocp-release@sha256:039a4ef7c128a049ccf916a1d68ce93e8f5494b44d5a75df60c85e9e7191dacc: unable to pull image: Error reading blob sha256:23302e52b49d49a0a25da8ea870bc1973e7d51c9b306f3539cd397318bd8b0a5: Invalid status code returned when fetching blob 503 (Service Unavailable)

Environment

  • Red Hat Enterprise Linux
  • Openshift Container Platform
  • Client system where the pull is being requested is behind a proxy which is making use of an AV scanner

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content