You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Layers could not be found. Even with -i dive won't start.
What you expected to happen:
No errors.
How to reproduce it (as minimally and precisely as possible): dive node:22@sha256:35a5dd72bcac4bce43266408b58a02be6ff0b6098ffa6f5435aeea980a8951d7 on an Apple ARM results in could not find 'blobs/sha256/f715b6c8c4fffd54af22e15764afcb686f56e2218f7c7325e8093eeb3e7afe24' in parsed layers.
Anything else we need to know?:
I suspect this has to do with node:22 maybe not being available for Apple ARM or the concrete image being an x86 one. Anyway this shouldn't prevent browsing the image's file system.
Environment:
OS version macOS 15.1.1
Docker version (if applicable) 27.3.1
The text was updated successfully, but these errors were encountered:
What happened:
Layers could not be found. Even with
-i
dive won't start.What you expected to happen:
No errors.
How to reproduce it (as minimally and precisely as possible):
dive node:22@sha256:35a5dd72bcac4bce43266408b58a02be6ff0b6098ffa6f5435aeea980a8951d7
on an Apple ARM results incould not find 'blobs/sha256/f715b6c8c4fffd54af22e15764afcb686f56e2218f7c7325e8093eeb3e7afe24' in parsed layers
.Anything else we need to know?:
I suspect this has to do with node:22 maybe not being available for Apple ARM or the concrete image being an x86 one. Anyway this shouldn't prevent browsing the image's file system.
Environment:
The text was updated successfully, but these errors were encountered: