Closed Franr closed 1 year ago
+1 on this. When I initialized a DockerClient using this as the base_url
the library worked as intended. When I tried to use client = docker.from_env()
, an error was thrown.
Fixes to these issues have been documented here: https://github.com/binbashar/le-ref-architecture-doc/pull/194
@kwesiRutledge that's still a PR but feel free to get the fixes from there until proper docs are released.
The documentation with the fix was merged and is available here: https://leverage.binbash.co/user-guide/troubleshooting/general/#leverage-cli-cant-find-the-docker-daemon
@diego-ojeda-binbash, thank you for your collaboration on this project. I've just published the latest documentation release here.
@kwesiRutledge Kwesi, I appreciate your feedback immensely. It's fantastic to see that you're most probably utilizing Leverage for your AWS projects. I'd like to extend an invitation for you to join our community Slack channel. It's a great place for prompt support and collaborative discussions on any future needs you might have. You can join us here.
Describe the Bug
If you run
leverage
onversion 24.0.6, build ed223bc
on Mac, apparently docker-py tries to connect to the docker socket on the wrong place.Expected Behavior
Rather than
/var/run/docker.sock
, we should try to establish the connection throughunix://$HOME/.docker/run/docker.sock
insteadEnvironment (please complete the following information):
Docker version 24.0.6, build ed223bc
leverage version 1.10.2
MacOS Ventura 13.5
Additional Context
https://github.com/docker/docker-py/issues/3146 https://docs.docker.com/desktop/release-notes/#4131 https://github.com/docker/for-mac/issues/6529 https://github.com/portainer/portainer/issues/9945#issuecomment-1654825596