Skip to content
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

Docker daemon provider doesn't support contexts #332

Open
wjam opened this issue Dec 13, 2024 · 0 comments
Open

Docker daemon provider doesn't support contexts #332

wjam opened this issue Dec 13, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@wjam
Copy link

wjam commented Dec 13, 2024

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 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):

  1. Use colima to manage Docker, rather than host.
  2. Make sure DOCKER_HOST is unset
  3. Attempt to do something like stereoscope.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:

  • OS (e.g: cat /etc/os-release or similar): Both latest macOS and Ubuntu 24.04.1 LTS
@wjam wjam added the bug Something isn't working label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

1 participant