Combining RUN commands in Docker - Time & Space Complexity

Time Complexity: Combining RUN commands

O(n)

Understanding Time Complexity

We want to understand how combining RUN commands in Dockerfiles affects the time it takes to build an image.

Specifically, how the number of commands influences the total build time.

Scenario Under Consideration

Analyze the time complexity of the following Dockerfile snippet.

FROM ubuntu:latest

RUN apt-get update
RUN apt-get install -y curl
RUN apt-get install -y git
RUN apt-get clean

This snippet runs four separate RUN commands to update, install curl, install git, and clean up.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Each RUN command creates a new layer and executes a shell command.
• How many times: Four separate RUN commands run sequentially.

How Execution Grows With Input

Each RUN command adds its own execution time and overhead.

Input Size (n)	Approx. Operations
1 RUN command	1 command execution + 1 layer creation
4 RUN commands	4 command executions + 4 layer creations
10 RUN commands	10 command executions + 10 layer creations

Pattern observation: The total build time grows roughly in direct proportion to the number of RUN commands.

Final Time Complexity

Time Complexity: O(n)

This means the build time grows linearly as you add more RUN commands.

Common Mistake

[X] Wrong: "Combining RUN commands will always make the build slower because it runs more commands together."

[OK] Correct: Combining commands reduces the number of layers and overhead, often making the build faster overall.

Interview Connect

Understanding how Docker layers and RUN commands affect build time helps you write efficient Dockerfiles and shows you think about performance in real projects.

Self-Check

"What if we combined all RUN commands into a single RUN with multiple commands joined by &&? How would the time complexity change?"