Since e9d5649, attempting to login to a container registry with the podman driver results in:

failed: [localhost] (item="workspace-src-ubuntu_focal registry username: ") => {"ansible_loop_var": "item", "changed": false, "item": {"image": "ghcr.io/image:tag", "name": "workspace-src-ubuntu_focal", "pre_build_image": true, "registry": {"credentials": {"password": ****, "username": *****}, "url": "ghcr.io"}}, "msg": "parameters are mutually exclusive: certdir|tlsverify"}

e9d5649 uses the containers.podman.podman_login module instead of using ansible.command to login to the registry. It appears that containers.podman.podman_login explicitly disallows setting the tlsverify and certdir arguments together -- no matter whether they are false/true. e9d5649 appears to set the parameters to an empty string even when they default to false.

Since this renders the podman plugin practically unusable, I propose:

1. to rollback the relevant part of e9d5649
2. open a bug report with https://github.com/containers/ansible-podman-collections.git if it is felt that it should be possible to set these two options together (I do not personally see the rational for making them mutually exclusive -- I think podman allows both?)
3. if this is fixed upstream, reinstate the use of the podman.podman_login