Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 6. Populating your private automation hub container registry

By default, private automation hub does not include automation execution environments. To populate your container registry, you must push an execution environment to it.

Before the new execution environment image can be used for automation jobs, it must be uploaded to the private automation hub.

Procedure

  1. First, verify that the execution environment image can be seen in the local podman cache: 

    $ podman images --format "table {{.ID}} {{.Repository}} {{.Tag}}"
IMAGE ID	    REPOSITORY					              TAG
b38e3299a65e	private-hub.example.com/custom-ee     	  latest
8e38be53b486	private-hub.example.com/ee-minimal-rhel8  latest
    Copy to Clipboard Toggle word wrap

  2. Then log in to the private automation hub’s container registry and push the image to make it available for use with job templates and workflows: 

    $ podman login private-hub.example.com -u admin
Password:
Login Succeeded!
$ podman push private-hub.example.com/custom-ee:latest
    Copy to Clipboard Toggle word wrap

Use the following workflow to populate your private automation hub remote registry:

  1. Pull execution environments for use in automation hub
  2. Tag execution environment for use in automation hub
  3. Push an execution environment to private automation hub
  4. Set up your container repository
  5. Add a README to your container repository
  6. Provide access to your automation execution environmentss
  7. Tag container images
  8. Create a credential
  9. Pulling images from a container repository
  10. Pull an image
  11. Sync images from a container repository
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top