ENTRYPOINT vs CMD difference in Docker - When to Use Which

The Big Idea

Discover how a small Docker tweak can save you from command confusion and errors!

The Scenario

Imagine you build a Docker image for your app, but every time you run a container, you have to remember the exact command and options to start it properly.

You try to run it with different commands, but sometimes it breaks or behaves unexpectedly.

The Problem

Manually specifying commands each time is slow and confusing.

You might forget the right command or accidentally override important defaults.

This leads to errors and wasted time fixing simple mistakes.

The Solution

Docker's ENTRYPOINT and CMD let you set default commands inside the image.

ENTRYPOINT defines the main command that always runs.

CMD provides default arguments that can be changed when running the container.

This makes running containers easier and more consistent.

Before vs After

✗ Before

docker run myapp python app.py
# Must remember full command every time

✓ After

ENTRYPOINT ["python", "app.py"]
CMD ["--help"]
# Run with defaults or add args like: docker run myapp --version

What It Enables

You can create flexible Docker images that run reliably with sensible defaults but still allow easy customization.

Real Life Example

A web server image uses ENTRYPOINT to always start the server program, while CMD sets the default port.

You can run the container with a different port without changing the image.

Key Takeaways

ENTRYPOINT sets the fixed command to run in the container.

CMD provides default arguments that can be overridden.

Together, they make Docker containers easier and safer to run.

Practice

1. What is the primary role of ENTRYPOINT in a Dockerfile?

easy

A. It provides default arguments for the command.

B. It specifies environment variables for the container.

C. It sets the main command that always runs when the container starts.

D. It defines the working directory inside the container.

Solution

1. Step 1: Understand ENTRYPOINT purpose

   ENTRYPOINT defines the main command that runs every time the container starts, making it fixed.

2. Step 2: Compare with CMD

   CMD provides default arguments or a default command only if ENTRYPOINT is not set, so it is not the main command itself.

3. Final Answer:

   It sets the main command that always runs when the container starts. -> Option C

4. Quick Check:

   ENTRYPOINT = main fixed command [OK]

Hint: ENTRYPOINT fixes the command, CMD sets defaults [OK]

Common Mistakes:

• Confusing CMD as the main command
• Thinking ENTRYPOINT sets environment variables
• Mixing ENTRYPOINT with working directory

2. Which of the following is the correct syntax to set ENTRYPOINT in a Dockerfile?

easy

A. ENTRYPOINT = "/bin/bash -c"

B. ENTRYPOINT ["/bin/bash", "-c"]

C. ENTRYPOINT [/bin/bash, "-c"]

D. ENTRYPOINT: /bin/bash -c

Solution

1. Step 1: Recall ENTRYPOINT syntax

   ENTRYPOINT uses JSON array syntax to specify the executable and its arguments, e.g. ["executable", "arg1"].

2. Step 2: Identify correct option

   ENTRYPOINT ["/bin/bash", "-c"] uses the correct JSON array format. Options A, B, and D use invalid syntax for Dockerfile ENTRYPOINT.

3. Final Answer:

   ENTRYPOINT ["/bin/bash", "-c"] -> Option B

4. Quick Check:

   ENTRYPOINT uses JSON array syntax [OK]

Hint: Use JSON array syntax for ENTRYPOINT [OK]

Common Mistakes:

• Using shell form without brackets for ENTRYPOINT
• Adding equal sign or colon incorrectly
• Using plain string without quotes

3. Given this Dockerfile snippet:

ENTRYPOINT ["echo"]
CMD ["Hello", "World"]

What will be the output when running the container without extra arguments?

medium

A. Hello World

B. echo Hello World

C. No output

D. Error: command not found

Solution

1. Step 1: Understand ENTRYPOINT and CMD interaction

   ENTRYPOINT sets the fixed command 'echo'. CMD provides default arguments 'Hello' and 'World'.

2. Step 2: Combine command and arguments

   Running the container runs 'echo Hello World', printing 'Hello World'.

3. Final Answer:

   Hello World -> Option A

4. Quick Check:

   ENTRYPOINT + CMD = echo Hello World [OK]

Hint: ENTRYPOINT command + CMD args run together [OK]

Common Mistakes:

• Thinking CMD overrides ENTRYPOINT command
• Expecting full command string printed
• Assuming no output without arguments

4. You wrote this Dockerfile:

ENTRYPOINT echo
CMD Hello World

But when you run the container, it produces unexpected output. What is the problem?

medium

A. Dockerfile must end with CMD, not ENTRYPOINT.

B. CMD cannot have multiple words without quotes.

C. ENTRYPOINT cannot be used with CMD.

D. ENTRYPOINT must be in JSON array form to avoid shell parsing errors.

Solution

1. Step 1: Check ENTRYPOINT syntax

   ENTRYPOINT without JSON array uses shell form, but 'echo' alone may cause parsing issues or unexpected behavior.

2. Step 2: Correct syntax requirement

   Using JSON array form like ["echo"] ensures proper command execution without shell interpretation errors.

3. Final Answer:

   ENTRYPOINT must be in JSON array form to avoid shell parsing errors. -> Option D

4. Quick Check:

   ENTRYPOINT needs JSON array for safety [OK]

Hint: Use JSON array for ENTRYPOINT to avoid errors [OK]

Common Mistakes:

• Using plain string ENTRYPOINT causing errors
• Misunderstanding CMD syntax rules
• Thinking ENTRYPOINT and CMD cannot be combined

5. You want a Docker container that always runs python app.py, but allows users to add extra arguments like --debug. How should you write ENTRYPOINT and CMD in the Dockerfile?

hard

A. ENTRYPOINT ["python", "app.py"] and CMD ["--debug"]

B. ENTRYPOINT ["python"] and CMD ["app.py", "--debug"]

C. CMD ["python", "app.py", "--debug"] only

D. ENTRYPOINT ["python", "app.py", "--debug"] only

Solution

1. Step 1: Fix main command with ENTRYPOINT

   Set ENTRYPOINT to ["python", "app.py"] so this command always runs.

2. Step 2: Provide default extra arguments with CMD

   Set CMD to ["--debug"] so users can override or add arguments when running the container.

3. Step 3: Understand combined behavior

   Docker runs ENTRYPOINT command plus CMD arguments, allowing flexibility with fixed main command.

4. Final Answer:

   ENTRYPOINT ["python", "app.py"] and CMD ["--debug"] -> Option A

5. Quick Check:

   ENTRYPOINT fixes command, CMD adds default args [OK]

Hint: ENTRYPOINT fixes command, CMD adds default args [OK]

Common Mistakes:

• Putting all commands in CMD only
• Using ENTRYPOINT without CMD for defaults
• Mixing order causing command override