Why Multiple FROM statements in Docker? - Purpose & Use Cases

The Big Idea

What if you could build your app in one place but run it in a completely different, lightweight environment?

The Scenario

Imagine you want to build a software image that needs two different environments: one to compile your code and another to run it. You try to install everything in one big image manually.

The Problem

This manual way makes your image huge, slow to build, and hard to maintain. You waste time downloading unnecessary tools and risk mixing incompatible software.

The Solution

Using multiple FROM statements lets you create separate stages in your Dockerfile. You build your code in one stage, then copy only the needed parts to a smaller final image. This keeps things clean and efficient.

Before vs After

✗ Before

FROM ubuntu:20.04
RUN apt-get update && apt-get install -y build-essential python3
COPY . /app
RUN make /app

✓ After

FROM build-image AS builder
COPY . /app
RUN make /app
FROM runtime-image
COPY --from=builder /app/bin /app/bin

What It Enables

You can create smaller, faster, and more secure images by separating build and runtime environments cleanly.

Real Life Example

A developer compiles a complex app with many tools, then ships only the final executable in a tiny image for production, saving bandwidth and startup time.

Key Takeaways

Manual single-stage images become large and slow.

Multiple FROM statements create build stages for efficiency.

Final images contain only what is needed to run the app.

Practice

1. What is the main purpose of using multiple FROM statements in a Dockerfile?

easy

A. To create multi-stage builds that reduce final image size

B. To run multiple containers at the same time

C. To specify different base images for different containers

D. To define environment variables for the container

Solution

1. Step 1: Understand the role of FROM in Dockerfile

   The FROM statement sets the base image for building a Docker image.

2. Step 2: Recognize multi-stage build benefits

   Using multiple FROM statements allows building in stages, copying only needed files to the final image, reducing size.

3. Final Answer:

   To create multi-stage builds that reduce final image size -> Option A

4. Quick Check:

   Multiple FROM = multi-stage build [OK]

Hint: Multiple FROM means multi-stage build for smaller images [OK]

Common Mistakes:

• Thinking multiple FROM runs multiple containers
• Confusing FROM with environment variable setting
• Assuming FROM defines runtime commands

2. Which of the following is the correct syntax to copy files from a previous build stage named builder?

easy

A. COPY --stage=builder /app/build /app

B. COPY --from=builder /app/build /app

C. COPY --source=builder /app/build /app

D. COPY --stage-name=builder /app/build /app

Solution

1. Step 1: Recall the correct COPY syntax for multi-stage

   The correct flag to copy from another stage is --from=stage_name.

2. Step 2: Match the option with correct syntax

   Only COPY --from=builder /app/build /app uses --from=builder, which is valid syntax.

3. Final Answer:

   COPY --from=builder /app/build /app -> Option B

4. Quick Check:

   Copy from stage uses --from [OK]

Hint: Use COPY --from=stage_name to copy files between stages [OK]

Common Mistakes:

• Using --stage or --source instead of --from
• Misspelling the flag name
• Omitting the equals sign (=) after --from

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

FROM node:18 AS builder
RUN npm install && npm run build
FROM nginx:alpine
COPY --from=builder /app/build /usr/share/nginx/html

medium

A. Final image includes full Node.js and npm layers, making it large

B. Final image will fail to build due to missing /app/build directory

C. Final image only contains nginx and the built files, keeping it small

D. Final image contains both Node.js and nginx running simultaneously

Solution

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

   The first stage builds the app with Node.js. The second stage uses nginx base image.

2. Step 2: Understand the COPY --from usage

   The built files from the builder stage are copied into nginx image, but Node.js layers are not included.

3. Final Answer:

   Final image only contains nginx and the built files, keeping it small -> Option C

4. Quick Check:

   Multi-stage copy keeps final image small [OK]

Hint: Final image excludes build tools if copied from previous stage [OK]

Common Mistakes:

• Assuming all build layers stay in final image
• Thinking COPY --from copies the entire image
• Confusing build failure with missing files

4. Identify the error in this Dockerfile snippet using multiple FROM statements:

FROM python:3.12 AS builder
RUN pip install -r requirements.txt
FROM alpine
COPY --from=build /app /app

medium

A. The stage name 'build' does not match the defined stage 'builder'

B. Alpine image cannot be used after python image

C. COPY command syntax is incorrect; missing destination path

D. pip install command should be in the second stage

Solution

1. Step 1: Check stage names in FROM statements

   The first stage is named 'builder', but COPY uses 'build' which is undefined.

2. Step 2: Understand COPY --from requires exact stage name

   Stage names must match exactly; otherwise, Docker throws an error.

3. Final Answer:

   The stage name 'build' does not match the defined stage 'builder' -> Option A

4. Quick Check:

   Stage names must match exactly in COPY --from [OK]

Hint: Match stage names exactly in COPY --from [OK]

Common Mistakes:

• Assuming similar names are accepted
• Thinking base image order matters here
• Ignoring COPY destination path correctness

5. You want to build a Docker image that compiles a Go application and then creates a minimal final image with only the compiled binary. Which Dockerfile snippet correctly uses multiple FROM statements to achieve this?

hard

A. FROM golang:1.20 AS builder
WORKDIR /app
COPY . .
RUN go build -o myapp
FROM scratch
COPY --from=builder /app/myapp /myapp
CMD ["/myapp"]

B. FROM golang:1.20
WORKDIR /app
COPY . .
RUN go build -o myapp
FROM alpine
COPY /app/myapp /myapp
CMD ["/myapp"]

C. FROM alpine AS builder
RUN apk add --no-cache go
WORKDIR /app
COPY . .
RUN go build -o myapp
FROM alpine
COPY --from=builder /app/myapp /myapp
CMD ["/myapp"]

D. FROM golang:1.20 AS builder
WORKDIR /app
COPY . .
RUN go build -o myapp
FROM alpine
COPY --from=builder /app/myapp /myapp
CMD ["/myapp"]

Solution

1. Step 1: Identify the build stage with Go compiler

   Stage named 'builder' uses golang image to compile the app.

2. Step 2: Use a minimal runtime image for final stage

   The final stage uses alpine (small image) and copies only the binary from builder.

3. Step 3: Verify COPY --from syntax and CMD

   COPY uses --from=builder to get binary; CMD runs the binary correctly.

4. Final Answer:

   FROM golang:1.20 AS builder WORKDIR /app COPY . . RUN go build -o myapp FROM alpine COPY --from=builder /app/myapp /myapp CMD ["/myapp"] -> Option D

5. Quick Check:

   Multi-stage build with builder and minimal final image [OK]

Hint: Use builder stage for compile, minimal image for final [OK]

Common Mistakes:

• Using scratch without proper setup
• Copying files without --from flag
• Building in final stage instead of builder