News for hackers. Stuff that matters.
Re:Dive – A tool for exploring each layer in a Docker image by IMTDb on Sunday November 25, 2018 @06:29PM (#18529770)
A docker image is built in layers that stack on top of each other. Think of each layer as a commit in a git repository.

This project takes an image and shows the list of layers (=commits) and for each layer (=commit) allow you to see what was changed (=the diff).

A bit like a git log for a docker image.

Re:Dive – A tool for exploring each layer in a Docker image by djsumdog on Monday November 26, 2018 @04:49AM (#18532192)
If OP looks up some Dockerfiles on docker hub, this will make more sense. Look at this mysql file for instance:

https://github.com/docker-library/mysql/blob/696fc899126ae00...

If two Dockerfiles use debain:stretch-slim as their base, docker won't download both base images twice. Each command in the Dockerfile creates an image. If you copy a Dockerfile and just change the last line and build them in order, the 2nd build will run a lot faster and you'll see in the output it pulls out "cached images" since it's already run those commands (docker build --no-cache always forced a full build).

If you start making Dockerfiles and playing around with it, it will start to make more sense.