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

add note about default socket to macos installation instructions #463

Closed
wants to merge 1 commit into from

Conversation

nigelwtf
Copy link

@nigelwtf nigelwtf commented Jul 20, 2023

This note should resolve #462 - and basically addresses the use case where MacOS users don't have the default socket option enabled in Docker Desktop - causing the (somewhat ambiguous) error Error response from daemon: pull access denied

Edit
and also resolve #453

@joaocasarin
Copy link

This shouldn't resolve #462. /var/run/docker.sock is available as following:
docker.sock -> /Users/joaocasarin/.docker/run/docker.sock

Even with that, it still doesn't work.

@jjmaestro
Copy link

Also, I think this PR would be superseded with #490 which actually makes dive honor the docker context :)

@nigelwtf
Copy link
Author

Also, I think this PR would be superseded with #490 which actually makes dive honor the docker context :)

Sweet. I'll just close this :)

@nigelwtf nigelwtf closed this Aug 20, 2024
joschi added a commit to joschi/dive that referenced this pull request 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 <[email protected]>
joschi added a commit to joschi/dive that referenced this pull request 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 <[email protected]>
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 this pull request may close these issues.

Unable to connect to docker.sock file while running dive Dive always fail when trying to fetch local image
3 participants