Docker Image Layers and Caching

How do Docker image layers work, and how can you optimize your Dockerfile to take advantage of layer caching?

Dockerintermediate

// interview question

How do Docker image layers work, and how can you optimize your Dockerfile to take advantage of layer caching?

Sample answer

Docker images are built from layers, where each instruction in a Dockerfile creates a new layer. Layers are cached and reused when possible. To optimize caching: order instructions from least to most frequently changing, copy dependency files before source code, use multi-stage builds, and leverage .dockerignore to exclude unnecessary files.

Why this matters

Layer caching is crucial for fast build times and efficient storage. When Docker builds an image, it checks if it can reuse cached layers. If a layer changes, all subsequent layers must be rebuilt. Understanding this mechanism helps you structure Dockerfiles for optimal build performance.

Code examples

Optimized Dockerfile with caching

dockerfile

# Bad: Source changes invalidate npm install cache
# FROM node:20-alpine
# COPY . .
# RUN npm install

# Good: Dependencies cached separately
FROM node:20-alpine
WORKDIR /app

# Copy only package files first
COPY package*.json ./
RUN npm ci --only=production

# Then copy source (changes here don't bust npm cache)
COPY . .

CMD ["node", "server.js"]

Inspect image layers

bash

# View image history and layer sizes
docker history myimage:latest

# Analyze image layers with dive
dive myimage:latest

# Build with cache info
docker build --progress=plain .

Common mistakes to avoid

Putting frequently changing files early in the Dockerfile, invalidating cache for subsequent layers
Not using .dockerignore, causing unnecessary cache invalidation when unrelated files change
Using COPY . . before installing dependencies