Satellite's registry does not listen at port 5000 for image pull

Solution Verified - Updated -


  • Upgrade to satellite 6.10 causing image pull failed from satellite registry. On the Satellite server, there is nothing listening on port 5000. So any request to satellite.local:5000 is failing.
  • Setting port 5000/tcp in containers-prepare-parameter.yaml makes deployment to fail since Satellite's container image registry does not listen at 5000/tcp.


  • Red Hat OpenStack Platform 16.x (RHOSP)
  • Red Hat Satellite 6.10

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