Live data from Hacker News

Dive – A tool for exploring each layer in a Docker image

github.com

1–10 of 45 posts

Re: Dive – A tool for exploring each layer in a Docker image

#2
This is amazing, thanks for sharing it! A very useful feature that I always missed but never actually tough about.

I've had a hard time understanding the slices on the beginning will be very useful for troubleshooting bad images also while optimizing image sizes.

Can probably help to understand problems like the one bug where the image size got almost a 2x increase after a CHOWN, because the slice is added again with different owner ( I think ;) ) would be so much easier to see with this.

Ref for the old bug https://github.com/moby/moby/issues/5505

Re: Dive – A tool for exploring each layer in a Docker image

#3
post #2

This is amazing, thanks for sharing it! A very useful feature that I always missed but never actually tough about. I've had a hard time understanding the slices on the beginning will be very useful for troubleshooting bad images also while optimizing image sizes. Can probably help to understand problems like the one bug where the image size got almost a 2x increase after a CHOWN, because the slice is added again with…

Same here. I'm relatively new to Docker. I've taken a public jessie image, and tweaked and committed locally. I can see that layers exist when I pull images, but just what they are has been a mystery.

Re: Dive – A tool for exploring each layer in a Docker image

#8
post #4

Nice!! have been waiting for something like this for a while. Gonna try this for sure.

just curious, how do you intend to use this? I mean, what problem does exploring each layer in a Docker solve for you?

"why does this small change increase the size of my image by 500mb"
Post reply on HN