> But Docker currently has a limitation in how it handles removing files in a build. After each build step, the intermediary state is committed as a layer, just

> But Docker currently has a limitation in how it handles removing files in a build. After each build step, the intermediary state is committed as a layer, just like a git commit. So removing files in a docker build is like removing files in git: they are still taking up space in the history. That's true unless you do the "everything in a single RUN statement" trick that is very popular.