Podman push to Private Automation Hub fails with "image not known" error

Solution In Progress - Updated -

Environment

  • Red Hat Ansible Automation Platform 2.x

Issue

  • Podman login to Private Automation Hub is successful. However, while pushing an image to PAH repository, it fails with an error Error: localhost/<image>: image not known.

    [root@controller ~]# podman push localhost/<custom_image>:latest
Error: localhost/<custom_image>: image not known

Resolution

  • Try pushing the AAP provided default images first, if the default images are getting pushed successfully then there is an issue with the custom image tagging. Retag the custom image correctly and push it to PAH again.

    # su - awx
$ podman tag localhost/<custom_image> hub_fqdn/<custom_image>  
$ podman push hub_fqdn/<custom_image> --tls-verify=false

Root Cause

  • The root cause of image not known error is incorrect tagging of the image. The image name should follow the repository name in order to push the same on that repository.

Diagnostic Steps

  • Try pushing the image from Controller server by tagging ee-minimal-rhel8 to hub web interface first in order to isolate the issue with PAH.

    # su - awx
$ podman tag registry.redhat.io/ansible-automation-platform-24/ee-minimal-rhel8 hub_fqdn/ee-minimal-rhel8 
$ podman push hub_fqdn/ee-minimal-rhel8 --tls-verify=false

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments