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.