-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Cannot analyze through docker desktop #495
Comments
I think this might be a docker desktop thing?
Running through the container (instead of the brew version) has the same result in both cases. |
Could you please try building |
(Some build instructions would help a bunch.) Does not seem to--built 326d463 and |
Download the fork, checkout the right branch from that fork and run |
By "some build instructions would help", I mean "I spent ten minutes fumbling through the makefile and eventually figured it out, which is not a great experience." |
Ah, sorry, thought it was aimed at me. I do agree with the sentiment, though. If you're up for diving deeper into the issue, I'd look at where is the socket for If not, please let me know, will see what I can do. |
|
Would you kindly try replacing that line in |
|
Alright, thanks! Until that's fixed I'd recommend saving the image to a file and then passing the archive to |
FYI, you don't have to change the |
@rajiv-k but if I'm reading it right, it's not working even after changing the host socket. |
@mark2185 try like this :D sudo ln -s /Users/yunsang/.docker/run/docker.sock /var/run/docker.sock |
I have the same problem and |
FWIW with Docker Desktop on Mac it's a symlink in
overriding DOCKER_HOST doesn't seem to make any difference for me. |
…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>
…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>
What happened:
I'm trying to analyze a multi-gigabyte local image, and it's just failing with "could not find image config"
What you expected to happen:
Analysis
How to reproduce it (as minimally and precisely as possible):
Honestly, I'm not sure what's going on to begin narrowing it down. It's a 3+GB image and not published to a registry.
Anything else we need to know?:
Some kind of
--verbose
might make tracking this down easier.Buildx is being used.
Environment:
The text was updated successfully, but these errors were encountered: