Multi-stage builds concept in Docker - Commands & Configuration

Introduction

Building Docker images can create large files if all build tools stay inside the final image. Multi-stage builds let you use multiple steps to build your app, keeping only the final needed parts. This makes images smaller and faster to use.

When you want to compile code inside a container but keep the final image small.

When your app needs build tools that are not needed at runtime.

When you want to separate build environment from runtime environment in one Dockerfile.

When you want to reduce image size to save bandwidth and storage.

When you want to speed up deployment by using smaller images.

Config File - Dockerfile

Dockerfile

FROM golang:1.20 AS builder
WORKDIR /app
COPY . .
RUN go build -o my-app

FROM alpine:3.18
WORKDIR /app
COPY --from=builder /app/my-app .
CMD ["./my-app"]

This Dockerfile has two stages:

• builder: Uses the golang image to compile the Go app.
• final: Uses a small Alpine Linux image and copies only the compiled app from the builder stage.

This keeps the final image small by excluding build tools.

Commands

Builds the Docker image using the Dockerfile in the current folder. It runs all stages and creates the final image named 'my-go-app'.

Terminal

docker build -t my-go-app .

Expected Output

[+] Building 10.3s (10/10) FINISHED

 => [internal] load build definition from Dockerfile

 => => transferring dockerfile: 137B

 => [internal] load .dockerignore

 => => transferring context: 2B

 => [internal] load metadata for docker.io/library/golang:1.20

 => [builder 1/4] FROM docker.io/library/golang:1.20@sha256:...

 => [builder 2/4] WORKDIR /app

 => [builder 3/4] COPY . .

 => [builder 4/4] RUN go build -o my-app

 => [final 1/3] FROM docker.io/library/alpine:3.18@sha256:...

 => [final 2/3] WORKDIR /app

 => [final 3/3] COPY --from=builder /app/my-app .

 => exporting to image

 => => exporting layers

 => => writing image sha256:...

 => => naming to docker.io/library/my-go-app

Shows the image named 'my-go-app' to verify it was created and to check its size.

Terminal

docker images my-go-app

Expected Output

REPOSITORY   TAG       IMAGE ID       CREATED          SIZE

my-go-app    latest    abcdef123456   10 seconds ago   12MB

Runs the container from the 'my-go-app' image to verify the app works as expected.

Terminal

docker run --rm my-go-app

Expected Output

Hello from my Go app!

→

--rm - Automatically removes the container after it stops to keep the system clean

Key Concept

If you remember nothing else from this pattern, remember: multi-stage builds let you separate building your app from running it, so your final Docker image stays small and efficient.

Common Mistakes

Copying source code directly into the final stage instead of copying only the built artifact.

This includes unnecessary build files and tools in the final image, making it large.

Use COPY --from=builder to copy only the compiled app or necessary files from the build stage.

Using a single stage Dockerfile with all build tools installed in the final image.

The final image becomes large and slower to deploy.

Use multi-stage builds to keep build tools only in the builder stage.

Summary

Multi-stage builds use multiple FROM statements to create separate build and final stages.

The final stage copies only the needed files from the build stage to keep the image small.

Build the image with docker build and verify it with docker images and docker run commands.

Practice

1. What is the main purpose of using multi-stage builds in Docker?

easy

A. To automatically update Docker images from the internet

B. To run multiple containers simultaneously

C. To create smaller and cleaner Docker images by separating build and runtime stages

D. To speed up the Docker daemon startup

Solution

1. Step 1: Understand multi-stage build concept

   Multi-stage builds allow splitting the Dockerfile into multiple stages, separating build tools from the final runtime environment.

2. Step 2: Identify the benefit

   This separation helps reduce image size by excluding unnecessary build dependencies from the final image.

3. Final Answer:

   To create smaller and cleaner Docker images by separating build and runtime stages -> Option C

4. Quick Check:

   Multi-stage builds = smaller images [OK]

Hint: Remember: multi-stage builds reduce image size by separating stages [OK]

Common Mistakes:

• Confusing multi-stage builds with running multiple containers
• Thinking it speeds up Docker daemon startup
• Believing it auto-updates images

2. Which of the following is the correct syntax to name a build stage in a Dockerfile?

easy

A. BUILD node AS builder

B. FROM node AS builder

C. STAGE node builder

D. COPY node AS builder

Solution

1. Step 1: Recall Dockerfile syntax for naming stages

   The correct syntax to name a build stage is using FROM <image> AS <stage-name>.

2. Step 2: Match options with syntax

   FROM node AS builder matches this syntax exactly, while others use invalid keywords.

3. Final Answer:

   FROM node AS builder -> Option B

4. Quick Check:

   Stage naming uses FROM ... AS ... [OK]

Hint: Use FROM ... AS ... to name stages in Dockerfile [OK]

Common Mistakes:

• Using BUILD or STAGE keywords instead of FROM
• Trying to name stages with COPY command
• Missing AS keyword

3. Given this Dockerfile snippet, what will be the size impact on the final image?

FROM golang:1.20 AS builder
WORKDIR /app
COPY . .
RUN go build -o myapp

FROM alpine:latest
COPY --from=builder /app/myapp /usr/local/bin/myapp
CMD ["myapp"]

medium

A. The final image will be small because only the built binary is copied from the builder stage

B. The final image will be large because it includes the entire Go build environment

C. The final image will be empty because no files are copied

D. The final image will contain source code but no binary

Solution

1. Step 1: Analyze the multi-stage build steps

   The first stage builds the Go binary using the full Go environment. The second stage uses a minimal Alpine image and copies only the binary from the builder stage.

2. Step 2: Understand image size impact

   Because only the binary is copied, the final image excludes the Go build tools and source code, making it small.

3. Final Answer:

   The final image will be small because only the built binary is copied from the builder stage -> Option A

4. Quick Check:

   Copying only binary = smaller final image [OK]

Hint: Copy only needed files from builder to reduce image size [OK]

Common Mistakes:

• Assuming the entire build environment is included in final image
• Thinking no files are copied
• Believing source code is copied without binary

4. Identify the error in this Dockerfile snippet using multi-stage builds:

FROM node:18 AS build
WORKDIR /app
COPY package.json .
RUN npm install
COPY . .
RUN npm run build

FROM nginx:alpine
COPY --from=build /app/dist /usr/share/nginx/html
RUN npm install
CMD ["nginx", "-g", "daemon off;"]

medium

A. CMD syntax is incorrect

B. The first stage misses the AS keyword for naming

C. COPY command syntax is invalid

D. The second stage incorrectly runs 'npm install' which is not available in nginx image

Solution

1. Step 1: Review commands in each stage

   The first stage builds the app correctly. The second stage uses nginx image, which does not have npm installed.

2. Step 2: Identify invalid command in second stage

   Running 'npm install' in the nginx stage will cause an error because npm is not present.

3. Final Answer:

   The second stage incorrectly runs 'npm install' which is not available in nginx image -> Option D

4. Quick Check:

   npm commands require node environment, not nginx [OK]

Hint: Check if commands match the base image environment [OK]

Common Mistakes:

• Assuming npm works in nginx image
• Missing AS keyword (actually present here)
• Misreading COPY syntax
• Confusing CMD syntax

5. You want to build a Docker image for a Python app using multi-stage builds. The first stage installs dependencies and runs tests. The second stage copies only the app and dependencies for runtime. Which Dockerfile snippet correctly implements this?

hard

A. FROM python:3.12 AS builder
WORKDIR /app
COPY requirements.txt .
RUN python -m venv venv && venv/bin/pip install -r requirements.txt
COPY . .
RUN venv/bin/pytest

FROM python:3.12-slim
WORKDIR /app
COPY --from=builder /app /app
CMD ["venv/bin/python", "app.py"]

B. FROM python:3.12
WORKDIR /app
COPY requirements.txt .
RUN pip install -r requirements.txt
COPY . .
RUN pytest
CMD ["python", "app.py"]

C. FROM python:3.12 AS builder
WORKDIR /app
COPY . .
RUN pytest

FROM python:3.12-slim
WORKDIR /app
COPY --from=builder /app /app
RUN pip install -r requirements.txt
CMD ["python", "app.py"]

D. FROM python:3.12 AS builder
WORKDIR /app
COPY requirements.txt .
RUN pip install -r requirements.txt
COPY . .
RUN pytest

FROM python:3.12-slim
WORKDIR /app
COPY --from=builder /app /app
RUN pip install -r requirements.txt
CMD ["python", "app.py"]

Solution

1. Step 1: Understand multi-stage build goals

   The first stage installs dependencies and runs tests. The second stage copies the app and dependencies for runtime only.

2. Step 2: Analyze each option

   FROM python:3.12 AS builder
   WORKDIR /app
   COPY requirements.txt .
   RUN python -m venv venv && venv/bin/pip install -r requirements.txt
   COPY . .
   RUN venv/bin/pytest
   
   FROM python:3.12-slim
   WORKDIR /app
   COPY --from=builder /app /app
   CMD ["venv/bin/python", "app.py"]

   installs dependencies in a venv and tests in builder, then copies all of /app (including venv) to slim image without reinstalling.

   FROM python:3.12
   WORKDIR /app
   COPY requirements.txt .
   RUN pip install -r requirements.txt
   COPY . .
   RUN pytest
   CMD ["python", "app.py"]

   has no multi-stage build.

   FROM python:3.12 AS builder
   WORKDIR /app
   COPY . .
   RUN pytest
   
   FROM python:3.12-slim
   WORKDIR /app
   COPY --from=builder /app /app
   RUN pip install -r requirements.txt
   CMD ["python", "app.py"]

   installs dependencies after copying, which is inefficient.

   FROM python:3.12 AS builder
   WORKDIR /app
   COPY requirements.txt .
   RUN pip install -r requirements.txt
   COPY . .
   RUN pytest
   
   FROM python:3.12-slim
   WORKDIR /app
   COPY --from=builder /app /app
   RUN pip install -r requirements.txt
   CMD ["python", "app.py"]

   reinstalls dependencies in second stage, increasing image size.

3. Final Answer:

   Uses virtualenv in builder stage to install dependencies and run tests, copies entire /app including venv to slim runtime -> Option A

4. Quick Check:

   Install and test in builder, copy to slim runtime [OK]

Hint: Install and test in builder, copy only needed files to slim image [OK]

Common Mistakes:

• Not using multi-stage builds
• Reinstalling dependencies in final stage
• Running tests in final image
• Copying unnecessary files