Container Image Pull Error: "Received unexpected HTTP status: 503 Service Unavailable"

Solution Verified - Updated -

Issue

Received unexpected HTTP status: 503 Service Unavailable

Image pull failing (using any of: podman/docker pull..., buildah bud..., skopeo copy...). There is an inconsistency where re-running the same command can work after some time.

Example of attempting to build an image that pulls from docker.io/library/python:3.12 using OpenShift Pipelines (same node) and buildah (similar occurs with OpenShift Dev Spaces):

Attempt #1

Attempt #2 (five minutes later)

Attempt #3 - Worked (One hour later). Fixed by Resolution #2, see below.

Environment

  • OpenShift Container Platform 4
  • OpenShift Pipelines
  • OpenShift Dev Spaces
  • podman, docker, skopeo, buildah

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