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

does not work with colima engine #397

Open
jeffzyliu opened this issue Apr 28, 2022 · 8 comments · May be fixed by #490
Open

does not work with colima engine #397

jeffzyliu opened this issue Apr 28, 2022 · 8 comments · May be fixed by #490

Comments

@jeffzyliu
Copy link

I built the same image on colima and docker desktop (Intel mac), and only the docker one worked. It sounds like lima isn't supported yet, so I'd like to request that feature in the future!

@jhogendorn
Copy link

I have also started swapping to colima due to docker-desktop reliability being pretty bad, and would love colima support.

In the meantime, you can run:

docker save myimage > image.tar
dive docker-engine://image.tar

@sammcj
Copy link

sammcj commented May 11, 2022

@jhogendorn dive docker-engine://image.tar doesn't seem to work for me after saving an image to a tar:

docker save my-valid-image:latest > image.tar

dive docker-engine://image.tar
Image Source: docker://docker-engine://image.tar
Fetching image... (this can take a while for large images)
Handler not available locally. Trying to pull 'docker-engine://image.tar'...
invalid reference format
cannot fetch image
exit status 1

@jhogendorn
Copy link

oh, apologies i mistyped.

dive docker-archive://image.tar

@TG-KK
Copy link

TG-KK commented Jul 27, 2022

A simple fix for this right now is just running sudo ln -sf ~/.colima/docker.sock /var/run/docker.sock every time after colima start

@saileshkotha
Copy link

A simple fix for this right now is just running sudo ln -sf ~/.colima/docker.sock /var/run/docker.sock every time after colima start

this works for me

@Trekoid
Copy link

Trekoid commented Aug 30, 2022

If you setup the DOCKER_HOST environment variable to point to colima in your shell configuration, dive (and other docker tools) will work out of the box. No need to manually update a symbolic link.

  1. Find the configuration file for your shell.
    • The default shell is Zsh on Macs. Your terminal configuration file is the ~/.zshrc file.
    • If you switched to Bash, your terminal configuration file is ~/.bashrc.
  2. Add export DOCKER_HOST=unix://$HOME/.colima/docker.sock to the file.
  3. Save and exit.
  4. Start a new terminal or run source ~/.zshrc or source ~/.bashrc to apply the changes to the existing terminal session.

@ErlanBelekov
Copy link

+1

@wujek-srujek
Copy link

According to colima FAQ what is missing in dive is support for Docker contexts (https://github.com/abiosoft/colima/blob/main/docs/FAQ.md#cannot-connect-to-the-docker-daemon-at-unixvarrundockersock-is-the-docker-daemon-running):
However, some applications are not aware of Docker contexts and may lead to the error.

joschi added a commit to joschi/dive that referenced this issue Nov 7, 2024
…oodman#490)

This patch adds support for detecting the "docker host" to connect to which is set in the current docker context.
One can have multiple such contexts and one of them can be activated via `docker context use <context-name>`.

Fixes wagoodman#397
Fixes wagoodman#408
Fixes wagoodman#412
Fixes wagoodman#463
Fixes wagoodman#495

Co-authored-by: Rajiv Kushwaha <raj25by10@gmail.com>
joschi added a commit to joschi/dive that referenced this issue Nov 7, 2024
…oodman#490)

This patch adds support for detecting the "docker host" to connect to which is set in the current docker context.
One can have multiple such contexts and one of them can be activated via `docker context use <context-name>`.

Fixes wagoodman#397
Fixes wagoodman#408
Fixes wagoodman#412
Fixes wagoodman#463
Fixes wagoodman#495

Co-authored-by: Rajiv Kushwaha <raj25by10@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants