Changes in containers.podman:1.14.0 require images be pushed to a namespace. Using this collection, images cannot reside in the root of a PAH or Registry.
The requirements.yml for this collection should either be version pinned to <1.14.0, or examples updated to indicate registry namespaces are required. However this is a breaking change for users and organizations not currently using registry namespaces for EEs.
Summary
Changes in containers.podman:1.14.0 require images be pushed to a namespace. Using this collection, images cannot reside in the root of a PAH or Registry.
https://github.com/containers/ansible-podman-collections/blob/1.14.0/plugins/modules/podman_image.py#L801
The requirements.yml for this collection should either be version pinned to <1.14.0, or examples updated to indicate registry namespaces are required. However this is a breaking change for users and organizations not currently using registry namespaces for EEs.
Issue Type
Ansible, Collection, Docker/Podman details
OS / ENVIRONMENT
RHEL 8.10, AAP 2.4.7
Desired Behavior
EE Build Role should function as normal using this role with an image destination such as:
pah.local/custom_ee:latest
Actual Behavior
Without specifying any additional registry destination paths/variables, error
Destination must be a full URL or path to a directory.
STEPS TO REPRODUCE
Using default example from this repository.
To use the above vars with
containers.podman > 1.13.0
you must changeee_registry_dest
from:to:
... or any other repository/namespace other than
ees