What is Docker layer caching?
Reusing the unchanged layers of a container image from an earlier build so a CI job rebuilds only what changed.
Docker layer caching in CI
A Docker image is built layer by layer, and a layer whose inputs have not changed can be reused. On a developer laptop this happens automatically. On an ephemeral CI runner the local layer cache is empty at the start of every job, so without help every build starts from the first instruction.
There are two families of fix. Exported caches save layers to a registry or to the CI cache and import them next time, paying a network transfer in both directions. Persistent caches keep the builder’s storage on a disk that is attached to the next job, so layers are simply there. Several runner providers offer the second as a feature. See Docker layer caching in CI.
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
CI Runners. (2026). What is Docker layer caching?. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/glossary/docker-layer-caching/