In Quay, podman pull errors out with 502 bad gateway

Solution Verified - Updated -

Issue

  • The command $ podman pull fails with the below error:

    $ podman pull <registry>/<image>:<tag>
    Trying to pull  <registry>/<image>:<tag>...
    Error: error pulling image " <registry>/<image>:<tag>": unable to pull <registry>/<image>:<tag>: unable to pull image: Error parsing 
    image configuration: Error fetching blob: invalid status code from registry 502 (Bad Gateway)
    
  • The following type of SSL errors related to botocore are seen in Quay pod logs while pulling images:

    ...
    gunicorn-registry stdout | ssl.SSLError: [X509] PEM lib (_ssl.c:4265)
    gunicorn-registry stdout | urllib3.exceptions.SSLError: [X509] PEM lib (_ssl.c:4265)
    gunicorn-registry stdout | botocore.exceptions.SSLError: SSL validation failed for https://s3.openshift- 
    storage.svc.cluster.local:443/quay-datastore-bcca0914-d071-474b-854a-2f0f4fe72491 [X509] PEM lib (_ssl.c:4265)
    ...
    

Environment

  • Red Hat Quay
    • 3.x

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