News for hackers. Stuff that matters.
Re:Dive – A tool for exploring each layer in a Docker image by cfontes on Sunday November 25, 2018 @03:09PM (#18528733)
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 by avip on Sunday November 25, 2018 @04:57PM (#18529321)
Newer docker versions have a --chown flag for COPY/ADD exactly to address that.
Re:Dive – A tool for exploring each layer in a Docker image by ravedave5 on Sunday November 25, 2018 @11:53PM (#18531174)
We added a lib to a java image and the size went up by about 4x the library size, I spent a few hours trying to track it down to no avail. Hopefully this will help pin down the issue.
Re:Dive – A tool for exploring each layer in a Docker image by dvdbloc on Monday November 26, 2018 @05:17AM (#18532307)
Let us know if it’s a relatable issue. Might save someone else a headache in the future.
Re:Dive – A tool for exploring each layer in a Docker image by mirimir on Sunday November 25, 2018 @03:57PM (#18528987)
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.