concept optimization in category docker
appears as: optimization, optimization

This is an excerpt from Manning's book Learn Docker in a Month of Lunches.
The second point is performance. Each stage in a multi-stage build has its own cache. Docker looks for a match in the image layer cache for each instruction; if it doesn’t find one, the cache is broken and all the rest of the instructions are executed--but only for that stage. The next stage starts again from the cache. You’ll be spending time structuring your Dockerfiles carefully, and when you get the optimization done, you’ll find 90% of your build steps use the cache.