-
Notifications
You must be signed in to change notification settings - Fork 104
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
Failure to pull with docker_compose_v2 despite authenticating previously #851
Comments
The docker_compose_v2(_pull) module doesn't do anything else than running You're using the docker_login module to authenticate. That module verifies that the credentials are correct by using the Now docker_compose_v2(_pull) can only use the credentials if it has access to the same credential store that docker_login stored them in. You are running Docker CLI from a Snap. My guess is that your Docker CLI setup does not use the same credentials store than docker_login (which uses code from Docker SDK for Python for accessing the credentials store). |
Thank you for the answer! |
Usually they do use the same context, unless you changed something. Are you maybe using Docker contexts? (I.e. does |
No...
|
In that case, no idea. I cannot replicate this with a regular registry. |
Thanks for the help. Any idea what I can try to progress? |
If you run
Yes, it works for me. BTW, I noticed that in the error message you posted:
there is a backslash |
SUMMARY
Pulling from private registry doesn't work after doing docker login
ISSUE TYPE
COMPONENT NAME
community.docker.docker_login
andcommunity.docker.docker_compose_v2
/community.docker.docker_compose_v2_pull module
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
After logging in, successfully being able to pull my images in private repository.
ACTUAL RESULTS
Failure to authenticate
The text was updated successfully, but these errors were encountered: