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

[BUG] podman login fails when missing docker configs #42

Open
nzwulfin opened this issue Aug 2, 2024 · 0 comments · May be fixed by #43
Open

[BUG] podman login fails when missing docker configs #42

nzwulfin opened this issue Aug 2, 2024 · 0 comments · May be fixed by #43
Labels
bug Something isn't working

Comments

@nzwulfin
Copy link

nzwulfin commented Aug 2, 2024

Version

redhat-actions/push-to-registry@v2

Describe the bug

When using a buildah or podman image without docker, the plugin fails writing a non-existent and unneeded credentials file even though the login was successful.

Steps to reproduce, workflow links, screenshots

Exporting REGISTRY_AUTH_FILE=/run/containers/0/auth.json
✍️ Writing registry credentials to "/root/.docker/config.json"
::error::Error: ENOENT: no such file or directory, open '/root/.docker/config.json'

There is a workaround from where this behavior was introduced in closing #18 but it doesn't make sense to me that I need to have a custom buildah image to support a tool that isn't installed or part of the workflow.

Podman doesn't use the docker config files, so if this is an attempt to support docker login in addition to podman login, then this should be probably be looked at again to not cause failures where not required. At the very least it shouldn't error the entire action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant