Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

podman login: tlsdir and certdir are mutually exclusive #248

Open
dometto opened this issue Mar 12, 2024 · 1 comment · May be fixed by #250
Open

podman login: tlsdir and certdir are mutually exclusive #248

dometto opened this issue Mar 12, 2024 · 1 comment · May be fixed by #250

Comments

@dometto
Copy link
Contributor

dometto commented Mar 12, 2024

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants