4 ms·

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

• manneshiva 8y ago
  just curious, how do you intend to use this? I mean, what problem does exploring each layer in a Docker solve for you?
  • deleted 8y ago
    [deleted]
  • orf 8y ago
    "why does this small change increase the size of my image by 500mb"
    • simonw 8y ago
      A few people pointed me to this dive tool after I wrote up these notes on shrinking Docker images: https://simonwillison.net/2018/Nov/19/smaller-python-docker-images/ https://simonwillison.net/2018/Nov/19/smaller-python-docker-...
  • wagoodman 8y ago
    It does two things for you: a) you get to visualize and explore the image layer by layer, and b) it will analyze and score the image with a % efficiency, listing all of the potential "inefficient" files. In this way it's not just showing you a score... the score doesn't help you make the image any better. This is why letting the user explore the layers is good, to help discover and explain why there is an inefficiency (not just that there is one).