Skip to content

Conversation

@aj0413
Copy link

@aj0413 aj0413 commented Nov 2, 2025

resolves broken feature introduced in #472

close #620

Tested to extract file from image and creates directory path starting from wherever dive was launched. Tested using README.md

Went ahead and figured out that the issue was in how the Image layer was being identified and passed down the stack.

Seems like the header.Name is the full 'blobs/sha256/[digest]' where as right now it just searches for an image named 'blobs'

image

NOTE: Further note that this only works when in the correct layer that adds/modifies the file

Tested with steps in issue, minimal dockerfile, and personal image. Used build on both MacOS (ARM) and Windows

@aj0413
Copy link
Author

aj0413 commented Nov 2, 2025

Looks like the feature still breaks when using file filter due to the node.path resolving to a memory issue of some kind

Tested removing regex filter for extract functionality. Seems to have resolved this issue

@aj0413 aj0413 changed the title fix: partially fix extract file functionality fix: extract file functionality Nov 3, 2025
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.

Crash when extracting a file

1 participant