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
Given the licensing around Docker desktop, I make use of Colima to run/manage Docker. Colima puts the Docker socket in ~/.colima/default/docker.sock and sets the currentContext in ~/.docker/config.json to colima. This means that there's no socket at the usual locations and so GetClient fails as it's unable to connect.
What you expected to happen:
stereoscope should support currentContext to discover the location of the Docker socket rather than assuming it's at /var/run/docker.sock
How to reproduce it (as minimally and precisely as possible):
What happened:
Given the licensing around Docker desktop, I make use of Colima to run/manage Docker. Colima puts the Docker socket in
~/.colima/default/docker.sock
and sets thecurrentContext
in~/.docker/config.json
tocolima
. This means that there's no socket at the usual locations and so GetClient fails as it's unable to connect.What you expected to happen:
stereoscope should support
currentContext
to discover the location of the Docker socket rather than assuming it's at/var/run/docker.sock
How to reproduce it (as minimally and precisely as possible):
DOCKER_HOST
is unsetstereoscope.GetImage("docker:ghcr.io/wjam/caddy-with-cloudflare:v0.0.4")
Anything else we need to know?:
A workaround for this is to set
DOCKER_HOST
to the correct location.Environment:
cat /etc/os-release
or similar): Both latest macOS andUbuntu 24.04.1 LTS
The text was updated successfully, but these errors were encountered: