You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a ansible playbook in order to launch docker containers.
The current requests 2.32.0 release (python) has introduced a breaking change for the Docker SDK for Python (docker/docker-py#3257).
The Docker SDK for Python team has addressed this issue in their version 7.1.0 release (https://github.com/docker/docker-py/releases/tag/7.1.0).
Maybe if we upgrade the Docker SDK for Python to version 7.1.0 in the resource of the formula ansible instead of 7.0.0 the problem could be solved ?
What happened (include all command output)?
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error connecting: Error while fetching server API version: Not supported URL scheme http+docker"}
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
I use a ansible playbook in order to launch docker containers.
The current requests 2.32.0 release (python) has introduced a breaking change for the Docker SDK for Python (docker/docker-py#3257).
The Docker SDK for Python team has addressed this issue in their version 7.1.0 release (https://github.com/docker/docker-py/releases/tag/7.1.0).
Maybe if we upgrade the Docker SDK for Python to version 7.1.0 in the resource of the formula ansible instead of 7.0.0 the problem could be solved ?
What happened (include all command output)?
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error connecting: Error while fetching server API version: Not supported URL scheme http+docker"}
What did you expect to happen?
The container should have been started.
Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: