How does Docker's layer caching work during a build?

Each instruction's cache key depends on the previous layer's digest, the instruction text, and (for COPY/ADD) a hash of the referenced files. If all three match a previous build, Docker reuses the cached layer rather than re-executing the instruction. The moment one instruction misses the cache, every subsequent instruction also misses, since each layer builds on the previous one's digest.