Builder pattern before multi-stage in Docker - Time & Space Complexity

Time Complexity: Builder pattern before multi-stage

O(n)

Understanding Time Complexity

We want to understand how the time to build a Docker image grows when using the builder pattern before multi-stage builds.

Specifically, how the build steps affect the total build time as the project size increases.

Scenario Under Consideration

Analyze the time complexity of the following Dockerfile snippet.

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

FROM nginx:alpine
COPY --from=builder /app/build /usr/share/nginx/html

This Dockerfile uses a builder stage to install dependencies and build the app, then copies the build output to a smaller image.

Identify Repeating Operations

Look for repeated or costly steps in the build process.

• Primary operation: Running npm install and npm run build which process all project files.
• How many times: Each command runs once per build, but their cost depends on project size.

How Execution Grows With Input

As the project size (number of files and dependencies) grows, the install and build steps take longer.

Input Size (n)	Approx. Operations
10 files	Small install and build time
100 files	Much longer install and build time
1000 files	Significantly longer install and build time

Pattern observation: Build time grows roughly proportional to project size because install and build process all files.

Final Time Complexity

Time Complexity: O(n)

This means the build time grows roughly in direct proportion to the size of the project files and dependencies.

Common Mistake

[X] Wrong: "The build time stays the same no matter how big the project is."

[OK] Correct: The install and build commands process all files and dependencies, so more files mean more work and longer build time.

Interview Connect

Understanding how build steps scale with project size helps you explain Docker build performance and optimization in real projects.

Self-Check

What if we split the build into multiple smaller stages? How would that affect the time complexity?

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