Builder pattern before multi-stage in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of multi-stage build simulation using builder pattern

Given the Dockerfile below simulating a builder pattern before multi-stage builds, what will be the output when running docker build .?

Docker

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

FROM node:18
WORKDIR /app
COPY --from=builder /app/dist ./dist
CMD ["node", "dist/index.js"]

A Build succeeds but final image contains all source files and node_modules

B Build fails due to COPY --from=builder syntax not supported before multi-stage

C Build succeeds and final image contains only /app/dist with built files

D Build fails because npm install is not run in final stage

💡 Hint

Consider how multi-stage builds isolate build artifacts from final image.

The Dockerfile uses multi-stage build syntax correctly. The first stage named 'builder' installs dependencies and builds the app. The final stage copies only the built files from the builder stage, resulting in a smaller final image.

🧠 Conceptual

intermediate

Why use builder pattern before multi-stage builds?

Before Docker supported multi-stage builds, why was the builder pattern used in Dockerfiles?

A To separate build dependencies from runtime dependencies and reduce final image size

B To enable parallel builds of multiple images simultaneously

C To allow running multiple containers from the same image

D To automatically update base images during build

💡 Hint

Think about how build tools and runtime environments differ.

The builder pattern was used to keep build tools and dependencies separate from the final runtime image, reducing image size and attack surface.

❓ Troubleshoot

advanced

Troubleshooting COPY --from error in Dockerfile

You have this Dockerfile simulating a builder pattern before multi-stage builds:

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

COPY --from=builder /app/dist ./dist
CMD ["node", "dist/index.js"]

What error will Docker produce when building this Dockerfile?

A Error: unknown flag: --from

B Error: missing 'AS builder' stage declaration

C No error, build completes successfully

D Error: COPY failed: stat /app/dist: no such file or directory

💡 Hint

Check if the build stage named 'builder' exists.

The COPY --from=builder requires a build stage named 'builder'. Without 'AS builder' in the first FROM line, Docker cannot find the source stage.

✅ Best Practice

advanced

Best practice for reducing final image size with builder pattern

Which approach best reduces the final Docker image size when using a builder pattern before multi-stage builds?

A Use a separate build container to compile artifacts, then copy only artifacts into a minimal runtime image

B Use a single Dockerfile stage with all build and runtime steps combined

C Install all dependencies in the final image to avoid missing packages

D Include source code and node_modules in the final image for debugging

💡 Hint

Think about what files are necessary to run the app versus build it.

Separating build and runtime environments keeps the final image small and secure by including only necessary runtime files.

🔀 Workflow

expert

Order of steps in builder pattern Dockerfile before multi-stage

Arrange the following Dockerfile steps in the correct order to implement a builder pattern before multi-stage builds:

A 1,3,2,4

B 1,2,3,4

C 2,3,1,4

D 2,1,3,4

💡 Hint

Consider what must be present before building and what is needed in the runtime.

First install dependencies, then copy source code, then build, and finally copy artifacts to runtime container.

Practice

1. What is the main purpose of the builder pattern in Docker before multi-stage builds were introduced?

easy

A. To run multiple containers simultaneously

B. To separate the build environment from the final runtime environment

C. To automatically update Docker images

D. To manage Docker volumes efficiently

Solution

1. Step 1: Understand the builder pattern concept

   The builder pattern splits the process into two parts: building the app and running it.

2. Step 2: Identify the benefit of separation

   This separation keeps the final image small by excluding build tools and files.

3. Final Answer:

   To separate the build environment from the final runtime environment -> Option B

4. Quick Check:

   Builder pattern = separate build and run [OK]

Hint: Builder pattern means build and run are separate stages [OK]

Common Mistakes:

• Confusing builder pattern with running multiple containers
• Thinking it manages volumes or updates automatically
• Assuming it is about Docker networking

2. Which Dockerfile snippet correctly implements the builder pattern before multi-stage builds?

easy

A. FROM node:14
WORKDIR /app
COPY . .
RUN npm install && npm run build
CMD ["npm", "start"]

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

C. FROM node:14
RUN npm install
COPY . .
CMD ["npm", "start"]

D. FROM nginx:alpine
COPY . /usr/share/nginx/html
RUN npm install

Solution

1. Step 1: Identify builder pattern before multi-stage

   Before multi-stage, builder pattern used separate Dockerfiles or manual copying, not the --from syntax.

2. Step 2: Check each option

   FROM node:14 AS builder WORKDIR /app COPY . . RUN npm install && npm run build FROM nginx:alpine COPY --from=builder /app/build /usr/share/nginx/html uses multi-stage syntax (--from=builder), which was not available before multi-stage builds.

3. Final Answer:

   FROM node:14 WORKDIR /app COPY . . RUN npm install && npm run build CMD ["npm", "start"] -> Option A

4. Quick Check:

   Before multi-stage, no --from usage [OK]

Hint: Before multi-stage, no --from in COPY command [OK]

Common Mistakes:

• Choosing multi-stage syntax before it existed
• Confusing build and runtime commands
• Ignoring the CMD instruction

3. Given this Dockerfile before multi-stage builds:

FROM node:14
WORKDIR /app
COPY . .
RUN npm install && npm run build
CMD ["node", "server.js"]

What is the likely size impact on the final image?

medium

A. The image will be large because build tools and source files remain

B. The image will be small because only build output is copied

C. The image size is minimal due to automatic cleanup

D. The image size depends only on the base image

Solution

1. Step 1: Analyze the Dockerfile steps

   The Dockerfile copies all source files and runs build inside the same image.

2. Step 2: Understand image size impact

   Since build tools and source files remain, the image size is larger than needed.

3. Final Answer:

   The image will be large because build tools and source files remain -> Option A

4. Quick Check:

   Single-stage build keeps all files, so image is large [OK]

Hint: Single-stage build keeps all files, making image large [OK]

Common Mistakes:

• Assuming build output only is copied
• Thinking Docker cleans up build files automatically
• Ignoring the COPY . . step

4. You have two Dockerfiles: one for building and one for running. You want to copy build artifacts from the builder image to the runtime build context manually. Which command correctly copies files from a stopped builder container named 'builder' to the runtime build context?

medium

A. docker cp ./build builder:/app/build

B. docker copy builder:/app/build ./build

C. docker cp builder:/app/build ./build

D. docker copy ./build builder:/app/build

Solution

1. Step 1: Understand docker cp syntax

   The correct syntax is 'docker cp <container>:<source_path> <destination_path>'.

2. Step 2: Match command to copy from container to local

   docker cp builder:/app/build ./build correctly copies from container 'builder' path to local './build'.

3. Final Answer:

   docker cp builder:/app/build ./build -> Option C

4. Quick Check:

   docker cp container:path local_path [OK]

Hint: Use 'docker cp container:path local_path' to copy files out [OK]

Common Mistakes:

• Using 'docker copy' instead of 'docker cp'
• Reversing source and destination paths
• Trying to copy from local to container incorrectly

5. You want to manually implement the builder pattern before multi-stage builds by using two Dockerfiles: Dockerfile.build and Dockerfile.run. Which sequence of commands correctly builds and prepares the final image with only the build output copied?

hard

A. docker build -f Dockerfile.build -t app-builder . && docker run --name builder app-builder && docker cp builder:/app/dist ./dist && docker rm builder && docker build -f Dockerfile.run -t app-runtime .

B. docker build -f Dockerfile.run -t app-runtime . && docker build -f Dockerfile.build -t app-builder .

C. docker build -f Dockerfile.run -t app-runtime . && docker run --name builder app-builder && docker cp builder:/app/dist ./dist

D. docker build -f Dockerfile.build -t app-builder . && docker create --name builder app-builder && docker cp builder:/app/dist ./dist && docker rm builder && docker build -f Dockerfile.run -t app-runtime .

Solution

1. Step 1: Build the builder image and create a container

   Use 'docker build' with Dockerfile.build, then 'docker create' to make a stopped container for copying files.

2. Step 2: Copy build output and build runtime image

   Copy files from the builder container, remove it, then build the runtime image with Dockerfile.run.

3. Final Answer:

   docker build -f Dockerfile.build -t app-builder . && docker create --name builder app-builder && docker cp builder:/app/dist ./dist && docker rm builder && docker build -f Dockerfile.run -t app-runtime . -> Option D

4. Quick Check:

   Build, create, copy, remove, then build runtime [OK]

Hint: Create container to copy files, then build runtime image [OK]

Common Mistakes:

• Using 'docker run' instead of 'docker create' for copying
• Building runtime image before copying build output
• Not removing temporary builder container