-
-
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
could not find image config #452
Comments
I'm guessing the format docker is outputing has changed slightly. Running it through skopeo allows it to be read by dive. Ex |
I did some digging and this is what I found. So this appears to be an issue with the docker version on an M1 mac. I looked at the tar file and it looks like it's the same issue as #318 |
Thanks. This was sort of what I guessed based on the code around the error. Would it be hard to fix to include all files? |
Just did some quick debugging and it seems the config starts with
|
@waterfoul thank you so much! For everyone else who's a little confused, this is the full set of commands to use:
|
I'm still having the same issue but on wsl2 with ubuntu 22.04
|
Having same on M1
|
Having same on m2 mac |
Same here
|
This worked for me: #444 (comment) |
I confirm @Birdie0's fix. Thanks! |
The workaround posted by @Birdie0 won't work with 25.0+ version (soon to be released).
dive/dive/image/docker/image_archive.go Line 79 in 3ef1dd2
A simple comparison of the different structure: v24$ docker save alpine | tar --list
3cc20332140056b331ad58185ab589c085f4e7d79d8c9769533d6a9b95d4b1b0.json
e863aefeb0c938ac2eb625d83bb2f5094568ba00a1ca521496a7a98f0e57ba27/
e863aefeb0c938ac2eb625d83bb2f5094568ba00a1ca521496a7a98f0e57ba27/VERSION
e863aefeb0c938ac2eb625d83bb2f5094568ba00a1ca521496a7a98f0e57ba27/json
e863aefeb0c938ac2eb625d83bb2f5094568ba00a1ca521496a7a98f0e57ba27/layer.tar
manifest.json
repositories v25$ docker save alpine | tar --list
blobs/
blobs/sha256/
blobs/sha256/0f3687eeb1f1f1aedfd67c8cad6a4f21b31527e25a40ffba9b6e7dd9d715e617
blobs/sha256/3cc20332140056b331ad58185ab589c085f4e7d79d8c9769533d6a9b95d4b1b0
blobs/sha256/4060ece20d7ac783f52cbe28a35fd5b06f90f7b4d773bae0d956024e85ff35b6
blobs/sha256/42d4e36ff7f1f6cfb53152ad3d1368436b78305b0d60dce03ae4230bf09bbcf3
blobs/sha256/579b34f0a95bb83b3acd6b3249ddc52c3d80f5c84b13c944e9e324feb86dd329
blobs/sha256/6ce9a9a256a3495ae60ab0059ed1c7aee5ee89450477f2223f6ea7f6296df555
blobs/sha256/8650cd65339b8a253f8b17ef7b63d4e2eb1ee05f00f2ae90aa74366e58ca45f7
blobs/sha256/9747b0f6f9fe54882e5e186e452150587460bf0a668738052302d10230052c77
blobs/sha256/bd218047ff719d3306f5565faa6f561ac3e52b51391804fd7b53231f8326f059
index.json
manifest.json
oci-layout As you can see, all image content (OCI index, OCI manifest, image config) are stored without any extension and are named according to their digest. A complete OCI image layour format is described here: https://github.com/opencontainers/image-spec/blob/main/image-layout.md |
Any viable solutions here for m1 users and Docker Desktop EDIT seems to work now after upgrading to Docker Desktop |
Won't work forever though, containerd is going to end up the default backend at some point. |
For anyone here on a newer version of docker-desktop upgrade to 0.12 |
ha? latest version of docker desktop is |
Version 0.12 of this tool: |
Installing version 0.12.0 works perfectly! Thanks 🙏 . I guess you can close this issue. |
yup 0.12.0 fixed my issues too 👏 |
I can confirm , works on mac m1 with latest :) (v0.12.0)
|
Encountering similar issue due to gzipped tar layer 243B sized in |
dive v0.12.0 didn't fix it for me but disabling containerd experimental "Features in Development" worked |
My docker got updated to 4.30.0 and I see that containerd is now defaulting to on. 0.12.0 didn't fix it for me either. |
@RangerRick Make sure you're running the latest version of dive with |
@Birdie0 there are two different issues. There was an issue with Docker that was resolved in dive 0.12.0. There is a 2nd issue (also #507) where the latest version of dive (0.12.0) still doesn't work when containerd storage is enabled. And Docker Desktop 4.30 made containerd storage the default. This is what @RangerRick was referring to |
Yeah, I can reproduce this with the latest Dive and Docker Desktop for Mac 4.30.0 on an M3 Macbook:
|
Oops, wait, looks like my issue is actually #507, so subtly different. |
Ah I see, my bad |
👋 Docker engineer here, we are not defaulting to containerd (yet) In 4.30 we did add a notification to make people aware this is something they can test but that's about it. |
When running Dive on "any" image, I get
could not find image config
. Same for every image I tried (with or without SHA hashes), e.gDocker pull and docker run works on images tried.
The text was updated successfully, but these errors were encountered: