ARO storage lockdown issues with the internal registry

Solution Verified - Updated -


Disclaimer: Links contained herein to external website(s) are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.

  • There is a known side-effect of the image registry storage lockdown feature deployed that prevents some users from accessing the image registry externally, which will manifest as a "podman push/pull" or an "oc image mirror" AuthorizationFailure error:

    Trying to pull
    Error: parsing image configuration: Error fetching blob: invalid status code from registry 403 (Forbidden)


  • Azure Red Hat OpenShift (ARO)
    • 4
  • OpenShift Managed (Azure)
    • 4

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