RUN instruction for executing commands in Docker - Time & Space Complexity

Time Complexity: RUN instruction for executing commands

O(n)

Understanding Time Complexity

We want to understand how the time it takes to run commands inside a Docker image grows as we add more commands.

How does adding more commands affect the total build time?

Scenario Under Consideration

Analyze the time complexity of the following Dockerfile snippet using RUN instructions.

FROM ubuntu:latest
RUN apt-get update && apt-get install -y curl
RUN echo "Hello World"
RUN mkdir /app
RUN touch /app/file1 /app/file2 /app/file3

This snippet runs several commands one after another during the image build.

Identify Repeating Operations

Look for repeated command executions or loops.

• Primary operation: Each RUN instruction executes commands sequentially.
• How many times: The number of RUN instructions equals the number of command groups run.

How Execution Grows With Input

As you add more RUN instructions, the total build time grows roughly in direct proportion.

Input Size (n)	Approx. Operations
2 RUN commands	2 command executions
5 RUN commands	5 command executions
10 RUN commands	10 command executions

Pattern observation: Doubling the number of RUN instructions roughly doubles the total execution time.

Final Time Complexity

Time Complexity: O(n)

This means the total time grows linearly with the number of RUN commands you add.

Common Mistake

[X] Wrong: "Adding more RUN commands won't affect build time much because they run fast."

[OK] Correct: Each RUN command adds extra steps and time, so more commands mean longer builds.

Interview Connect

Understanding how build steps add up helps you write efficient Dockerfiles and shows you think about performance in real projects.

Self-Check

"What if we combined multiple commands into a single RUN instruction? How would the time complexity change?"

Practice

1. What does the RUN instruction do in a Dockerfile?

easy

A. Executes commands during the image build process

B. Starts a container from an image

C. Copies files from host to container

D. Defines environment variables for the container

Solution

1. Step 1: Understand Dockerfile instructions

   The RUN instruction is used to execute commands while building the Docker image.

2. Step 2: Differentiate from other instructions

   Other instructions like COPY or ENV serve different purposes, not command execution.

3. Final Answer:

   Executes commands during the image build process -> Option A

4. Quick Check:

   RUN = execute commands during build [OK]

Hint: RUN runs commands while building the image [OK]

Common Mistakes:

• Confusing RUN with CMD or ENTRYPOINT
• Thinking RUN starts containers
• Mixing RUN with COPY or ENV

2. Which of the following is the correct syntax to install curl using RUN in a Debian-based Docker image?

easy

A. RUN apt-get install curl

B. RUN apt-get update && apt-get install -y curl

C. RUN install curl

D. RUN curl install

Solution

1. Step 1: Understand package installation in Debian

   Before installing packages, you must update the package list using apt-get update.

2. Step 2: Use correct flags and chaining

   The -y flag auto-confirms installation, and chaining commands with && ensures update runs before install.

3. Final Answer:

   RUN apt-get update && apt-get install -y curl -> Option B

4. Quick Check:

   Update then install with -y flag [OK]

Hint: Always update before install and use -y flag [OK]

Common Mistakes:

• Skipping apt-get update
• Not using -y to auto-confirm
• Wrong command order or syntax

3. Given this Dockerfile snippet:

FROM ubuntu:latest
RUN echo "Hello" && echo "World"

What will be the output when building this Docker image?

medium

A. Hello World printed during build

B. No output shown during build

C. Error because of missing semicolon

D. Only 'Hello' printed, 'World' ignored

Solution

1. Step 1: Analyze the RUN command chaining

   The command uses && to run two echo commands sequentially during build.

2. Step 2: Understand Docker build output

   During build, the output of RUN commands is shown in the terminal, so both 'Hello' and 'World' will print.

3. Final Answer:

   Hello World printed during build -> Option A

4. Quick Check:

   RUN shows command output during build [OK]

Hint: RUN output appears during build, && runs commands sequentially [OK]

Common Mistakes:

• Thinking RUN output is hidden
• Confusing && with ;
• Assuming only first command runs

4. Identify the error in this Dockerfile RUN instruction:

RUN apt-get update & apt-get install -y git

medium

A. RUN cannot have multiple commands

B. Missing -y flag for apt-get install

C. apt-get update should be last command

D. Using single & instead of && causes syntax error

Solution

1. Step 1: Check command chaining syntax

   Single & runs command in background and is invalid in Docker RUN; && is needed to chain commands properly.

2. Step 2: Confirm correct chaining for sequential execution

   Using && ensures the second command runs only if the first succeeds.

3. Final Answer:

   Using single & instead of && causes syntax error -> Option D

4. Quick Check:

   Use && to chain commands in RUN [OK]

Hint: Use && not & to chain commands in RUN [OK]

Common Mistakes:

• Using & instead of &&
• Ignoring command chaining rules
• Assuming RUN runs commands in parallel

5. You want to reduce Docker image layers by combining multiple commands in a single RUN instruction. Which is the best way to do this?

hard

A. Use multiple RUN instructions, one per command

B. Separate commands with semicolons in multiple RUN lines

C. Chain commands with && inside one RUN instruction

D. Use CMD instead of RUN for multiple commands

Solution

1. Step 1: Understand Docker image layers

   Each RUN instruction creates a new image layer, increasing image size.

2. Step 2: Combine commands to reduce layers

   Chaining commands with && inside one RUN instruction runs them sequentially in a single layer.

3. Final Answer:

   Chain commands with && inside one RUN instruction -> Option C

4. Quick Check:

   Combine commands with && to reduce layers [OK]

Hint: Chain commands with && in one RUN to reduce layers [OK]

Common Mistakes:

• Using multiple RUNs increases layers
• Using CMD instead of RUN for build steps
• Separating commands with semicolons without chaining