-
Notifications
You must be signed in to change notification settings - Fork 120
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
New requests release breaks docker version check #863
Comments
Are you sure that you were using The only modules that still have this problem are the modules using Docker Swarm, and the deprecated docker_compose module. |
#864 contains a fix for requests 2.32.2+; the current fix will stop working with 2.32.2. |
(community.docker.docker_container_info hasn't been relying on Docker SDK for Python since community.docker 3.0.0 btw. Instead it's using code from a vendored copy of that SDK.) |
Thanks for the quick reply. After checking again, I did have another installation of ansible collections at If I skip the |
community.docker 3.10.1 does not work with requests 2.32.2, it only works with requests 3.32.0 and 3.32.1. You need community.docker 3.10.2, which works with all requests 2.32.x releases. |
Alright, it worked indeed. 👍 But this also means that the new |
Yes, that's unfortunately needed. Also you need to make sure to remove the manually installed version once a new |
SUMMARY
requests==2.32.0
introduced a bug that affects the docker pip package.This results in
community.docker.docker_container_info
being broken at the moment. Other modules might be affected too.ISSUE TYPE
COMPONENT NAME
community.docker.docker_container_info
ANSIBLE VERSION
COLLECTION VERSION
STEPS TO REPRODUCE
I used ansible to install the
docker
pip package:And since the package did not specify an exact
requests
version it pulled down the latest2.32.0
.Later in the playbook trying to get information about a docker container:
Results in an error:
FIX
I was able to fix it temporarily by running:
Warning
For me it was necessary to use
sudo
for both the installation and uninstall as ansible is also running as root, so that I target packages in the same location.A permanent fix should also arrive soon, just wanted to document the issue in case someone encounters it in the meantime.
The text was updated successfully, but these errors were encountered: