Docker Run Command

The Docker run command is one of the most important and frequently used commands in Docker. It is the primary way to create and start containers from Docker images. Whether you are a beginner learning Docker basics or an intermediate user working with real-world applications, understanding the docker run command is essential.

This guide explains the Docker run command in a clear, structured, and practical way. You will learn its syntax, commonly used options, real-world examples, and best practices that align with modern containerization workflows.

What Is the Docker Run Command?

The Docker run command is used to:

• Create a new container from a Docker image
• Configure the container using command-line options
• Start the container and execute a command inside it

In simple terms, docker run combines multiple Docker actions into a single command:

• Pull the image (if not already available locally)
• Create a container from the image
• Start the container
• Run a specified process inside the container

Basic Syntax of Docker Run Command

📄
docker run [OPTIONS] IMAGE [COMMAND] [ARGUMENTS]

Understanding the Syntax

• OPTIONS: Flags that configure container behavior
• IMAGE: The Docker image to use
• COMMAND: Optional command to run inside the container
• ARGUMENTS: Arguments passed to the command

Simple Docker Run Example

📄
docker run hello-world

This example:

• Downloads the hello-world image if it is not present
• Creates a container
• Runs a test program
• Stops the container after execution

This is often the first command used to verify a Docker installation.

Running an Interactive Container

Interactive containers allow you to interact with a running process, such as a shell.

📄
docker run -it ubuntu

Explanation

• -i: Keeps standard input open
• -t: Allocates a pseudo-terminal
• ubuntu: Image name

This command starts an Ubuntu container and gives you access to the shell.

Running Containers in Detached Mode

Detached mode runs containers in the background.

📄
docker run -d nginx

Why Use Detached Mode?

• Ideal for web servers and background services
• Prevents blocking the terminal
• Common in production environments

Port Mapping with Docker Run

Port mapping allows external access to services running inside containers.

📄
docker run -d -p 8080:80 nginx

How Port Mapping Works

Now you can access Nginx at http://localhost:8080.

Using Environment Variables in Docker Run

Environment variables are commonly used to configure applications.

📄
docker run -e APP_ENV=production -e DB_HOST=localhost myapp

Use Cases

• Application configuration
• Database credentials
• Environment-specific settings

Mounting Volumes with Docker Run

Volumes persist data beyond the container lifecycle.

📄
docker run -v /host/data:/container/data ubuntu

Benefits of Volumes

• Persistent data storage
• Easy data sharing between containers
• Essential for databases and logs

Naming Containers

By default, Docker assigns random container names. You can define your own.

📄
docker run --name webserver nginx

Why Name Containers?

• Easier container management
• Simpler scripting and automation
• Clear identification in logs

Restart Policies in Docker Run

Restart policies help keep containers running.

📄
docker run --restart always nginx

Common Restart Policies

• no: Default behavior
• always: Restart regardless of exit status
• on-failure: Restart only on errors
• unless-stopped: Restart unless manually stopped

Docker Run vs Docker Start

Real-World Use Cases of Docker Run Command

Web Application Deployment

Running a web server like Nginx or Apache.

📄
docker run -d -p 80:80 nginx

Database Containers

📄
docker run -d -e MYSQL_ROOT_PASSWORD=secret mysql

Development Environments

Quickly spin up isolated environments for testing.

Best Practices for Using Docker Run

• Use explicit container names
• Prefer detached mode for services
• Use volumes for persistent data
• Limit resource usage when needed
• Clean up unused containers

By learning its syntax, options, and real-world applications, you gain full control over how containers are created and managed.

Frequently Asked Questions (FAQs)

1. What does the Docker run command do?

The Docker run command creates a new container from an image and starts it. It can also pull the image if it does not exist locally.

2. What is the difference between docker run and docker start?

Docker run creates and starts a container, while docker start only starts an existing stopped container.

3. How do I run a Docker container in the background?

Use the -d option to run the container in detached mode.

4. How can I expose container ports?

Use the -p option to map host ports to container ports.

5. Can I pass environment variables using Docker run?

Yes, environment variables can be passed using the -e option to configure applications inside containers.

Conclusion

The Docker run command is the foundation of working with Docker containers. From running simple test images to deploying production-ready services, mastering docker run helps you understand container lifecycle, configuration, and runtime behavior.