CMD instruction for default command in Docker - Time & Space Complexity

Time Complexity: CMD instruction for default command

O(1)

Understanding Time Complexity

We want to understand how the time it takes to run a Docker container changes when using the CMD instruction.

Specifically, how does the default command affect execution time as input changes?

Scenario Under Consideration

Analyze the time complexity of this Dockerfile snippet.

FROM ubuntu:latest
CMD ["echo", "Hello World"]

This sets a default command that prints "Hello World" when the container runs.

Identify Repeating Operations

Look for any repeated actions inside the CMD instruction.

• Primary operation: Running the echo command once.
• How many times: Exactly one time per container start.

How Execution Grows With Input

The command runs once regardless of input size.

Input Size (n)	Approx. Operations
10	1
100	1
1000	1

Pattern observation: The number of operations stays the same no matter the input size.

Final Time Complexity

Time Complexity: O(1)

This means the command runs in constant time, no matter how big or small the input is.

Common Mistake

[X] Wrong: "The CMD command runs multiple times or depends on input size."

[OK] Correct: The CMD instruction runs only once when the container starts, so its execution time does not grow with input size.

Interview Connect

Understanding how default commands run helps you explain container startup behavior clearly and confidently.

Self-Check

What if the CMD runs a script that loops over a list of files? How would the time complexity change?

Practice

1. What is the main purpose of the CMD instruction in a Dockerfile?

easy

A. To expose network ports

B. To set the default command that runs when the container starts

C. To copy files into the container

D. To define environment variables

Solution

1. Step 1: Understand the role of CMD

   The CMD instruction specifies the default command to run inside the container when it starts.

2. Step 2: Differentiate from other instructions

   Other instructions like COPY, EXPOSE, and ENV serve different purposes unrelated to the default command.

3. Final Answer:

   To set the default command that runs when the container starts -> Option B

4. Quick Check:

   CMD sets default command = C [OK]

Hint: CMD sets container's default run command [OK]

Common Mistakes:

• Confusing CMD with COPY or ENV
• Thinking CMD exposes ports
• Assuming CMD sets environment variables

2. Which of the following is the correct exec form syntax for the CMD instruction to run nginx as the default command?

easy

A. CMD ["nginx"]

B. CMD {"nginx"}

C. CMD ("nginx")

D. CMD nginx

Solution

1. Step 1: Recall CMD syntax forms

   Docker supports two CMD forms: shell form (string) and exec form (JSON array). The exec form is recommended for clarity and safety.

2. Step 2: Identify correct JSON array syntax

   The correct JSON array syntax uses square brackets and double quotes: CMD ["nginx"]. Other options use invalid syntax.

3. Final Answer:

   CMD ["nginx"] -> Option A

4. Quick Check:

   CMD JSON array uses brackets and quotes = D [OK]

Hint: Use JSON array with brackets and quotes for CMD [OK]

Common Mistakes:

• Using parentheses or curly braces instead of brackets
• Omitting quotes around command
• Using shell form without quotes causing errors

3. Given this Dockerfile snippet:

FROM alpine
CMD ["echo", "Hello World"]

What will be the output when you run the container without overriding the command?

medium

A. No output, container exits silently

B. echo Hello World

C. Hello World

D. Error: command not found

Solution

1. Step 1: Understand CMD execution

   The CMD instruction runs echo with argument Hello World as the default command inside the container.

2. Step 2: Predict container output

   Running the container executes echo "Hello World", which prints Hello World to the console.

3. Final Answer:

   Hello World -> Option C

4. Quick Check:

   CMD runs echo with args = Hello World [OK]

Hint: CMD JSON array runs command with args exactly [OK]

Common Mistakes:

• Thinking CMD prints the command itself
• Assuming no output without explicit print
• Confusing CMD with ENTRYPOINT behavior

4. Identify the best practice issue in this Dockerfile snippet:

FROM ubuntu
CMD echo Hello World

medium

A. Missing quotes around Hello World

B. FROM instruction is incorrect

C. CMD cannot run echo command

D. CMD should be in JSON array form for best practice

Solution

1. Step 1: Check CMD syntax

   The CMD instruction here uses shell form without quotes, which is allowed but less safe and less clear.

2. Step 2: Recommend JSON array form

   Best practice is to use JSON array form like CMD ["echo", "Hello World"] to avoid shell parsing issues.

3. Final Answer:

   CMD should be in JSON array form for best practice -> Option D

4. Quick Check:

   Use JSON array for CMD best practice = B [OK]

Hint: Prefer JSON array form for CMD to avoid shell issues [OK]

Common Mistakes:

• Thinking shell form is invalid syntax
• Assuming quotes are mandatory in shell form
• Believing CMD cannot run simple commands

5. You have this Dockerfile:

FROM node:18
CMD ["node", "app.js"]

You want to override the default command to run node test.js when starting the container. Which command will do this correctly?

hard

A. docker run myimage node test.js

B. docker run myimage CMD ["node", "test.js"]

C. docker run myimage --cmd node test.js

D. docker run myimage run node test.js

Solution

1. Step 1: Understand CMD override

   When running a container, any command after the image name overrides the Dockerfile CMD instruction.

2. Step 2: Identify correct docker run syntax

   The correct syntax is docker run myimage node test.js. Options with CMD or --cmd flags are invalid.

3. Final Answer:

   docker run myimage node test.js -> Option A

4. Quick Check:

   Override CMD by adding command after image name = A [OK]

Hint: Override CMD by adding command after image name in docker run [OK]

Common Mistakes:

• Using CMD or --cmd flags in docker run
• Placing command before image name
• Using invalid docker run syntax