Difference between RUN and CMD in a Dockerfile

docker dockerfile
TakeSoUp picture TakeSoUp · May 26, 2016 · Viewed 104.7k times · Source

I'm confused about when should I use CMD vs RUN. For example, to execute bash/shell commands (i.e. ls -la) I would always use CMD or is there a situation where I would use RUN? Trying to understand the best practices about these two similar Dockerfile directives.

Answer

Matt picture Matt · May 26, 2016

RUN is an image build step, the state of the container after a RUN command will be committed to the container image. A Dockerfile can have many RUN steps that layer on top of one another to build the image.

CMD is the command the container executes by default when you launch the built image. A Dockerfile will only use the final CMD defined. The CMD can be overridden when starting a container with docker run $image $other_command.

ENTRYPOINT is also closely related to CMD and can modify the way a container starts an image.

Related questions

How do I pass environment variables to Docker containers?

I'm new to Docker, and it's unclear how to access an external database from a container. Is the best way to hard-code in the connection string? # Dockerfile ENV DATABASE_URL amazon:rds/connection?string

Read More
What is the difference between the 'COPY' and 'ADD' commands in a Dockerfile?

What is the difference between the COPY and ADD commands in a Dockerfile, and when would I use one over the other? COPY <src> <dest> The COPY instruction will copy new files from <src> …

Read More
How to set image name in Dockerfile?

You can set image name when building a custom image, like this: docker build -t dude/man:v2 . # Will be named dude/man:v2 Is there a way to define the name of the image in Dockerfile, so I don't …

Read More