Running containers in detached mode in Docker - Step-by-Step Execution

Process Flow - Running containers in detached mode

Start Docker Container Command

↓

Check for -d flag?

No→Run container in foreground

Yes↓

Run container in detached mode

↓

Container runs in background

↓

Return container ID

↓

User can continue using terminal

This flow shows how Docker decides to run a container in detached mode when the -d flag is used, allowing the container to run in the background and freeing the terminal.

Execution Sample

Docker

docker run -d nginx

docker ps

Run an nginx container in detached mode and then list running containers.

Process Table

Step	Command	Action	Output/Result
1	docker run -d nginx	Check for -d flag	Flag found, proceed to detached mode
2	docker run -d nginx	Start container in background	Container starts, terminal freed
3	docker run -d nginx	Return container ID	Outputs container ID string
4	docker ps	List running containers	Shows nginx container running with container ID
5	End	No more commands	User terminal ready for new commands

💡 Container runs in background; terminal is free for new commands

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
container_mode	none	detached	detached	detached
container_id	none	generated_id	generated_id	generated_id
terminal_state	busy	free	free	free

Key Moments - 3 Insights

Why does the terminal become free immediately after running 'docker run -d nginx'?

Because the -d flag tells Docker to run the container in detached mode, so it runs in the background and does not block the terminal. See execution_table step 2.

What does Docker output after starting a container in detached mode?

Docker outputs the container ID string so you can identify or manage the container later. See execution_table step 3.

How can you verify that the container is running after starting it detached?

By running 'docker ps' which lists all running containers, showing the nginx container with its ID. See execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution table, what is the terminal state immediately after step 2?

A busy

B free

C unknown

D waiting

💡 Hint

Check the 'terminal_state' variable in variable_tracker after Step 2

At which step does Docker output the container ID?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Output/Result' column in execution_table for container ID output

If you remove the -d flag, what will happen to the terminal after running 'docker run nginx'?

A Docker will output container ID and exit

B Terminal will be free immediately

C Terminal will stay busy until container stops

D Container will not start

💡 Hint

Refer to concept_flow where absence of -d flag leads to foreground running

Concept Snapshot

docker run -d <image>
- Runs container in detached mode (background)
- Terminal is free immediately
- Outputs container ID
- Use 'docker ps' to see running containers

Full Transcript

When you run 'docker run -d nginx', Docker checks for the -d flag. Because it is present, Docker starts the nginx container in detached mode, meaning it runs in the background. The terminal becomes free immediately, allowing you to run other commands. Docker outputs the container ID so you can identify the container later. You can verify the container is running by using 'docker ps', which lists all running containers including the nginx one. Without the -d flag, the container runs in the foreground and the terminal stays busy until the container stops.

Practice

1. What does running a Docker container with the -d option do?

easy

A. Runs the container in detached mode, in the background

B. Runs the container interactively with a terminal

C. Removes the container after it stops

D. Builds a new Docker image from a Dockerfile

Solution

1. Step 1: Understand the -d option meaning

   The -d flag tells Docker to run the container in detached mode, meaning it runs in the background.

2. Step 2: Compare with other options

   Other options like interactive mode (-it) keep the container attached to the terminal, which is different from detached mode.

3. Final Answer:

   Runs the container in detached mode, in the background -> Option A

4. Quick Check:

   Detached mode = background run [OK]

Hint: Remember: -d means detach and run in background [OK]

Common Mistakes:

• Confusing -d with -it for interactive mode
• Thinking -d removes the container
• Mixing up build and run commands

2. Which of the following is the correct syntax to run a container named myapp in detached mode using the image nginx?

easy

A. docker run nginx -d --name myapp

B. docker run -d --name myapp nginx

C. docker run --detach myapp nginx

D. docker run --name myapp -it nginx

Solution

1. Step 1: Identify correct order and flags

   The correct syntax places options before the image name. The -d flag enables detached mode, and --name myapp names the container.

2. Step 2: Validate each option

   docker run -d --name myapp nginx correctly uses docker run -d --name myapp nginx. docker run --detach myapp nginx misplaces arguments, docker run nginx -d --name myapp places flags after image, and docker run --name myapp -it nginx uses interactive mode instead of detached.

3. Final Answer:

   docker run -d --name myapp nginx -> Option B

4. Quick Check:

   Options before image, -d for detached [OK]

Hint: Put all flags before the image name in docker run [OK]

Common Mistakes:

• Placing flags after the image name
• Using -it instead of -d for detached mode
• Misusing --detach instead of -d

3. What will be the output of the command docker ps after running docker run -d nginx?

medium

A. Shows the logs of the nginx container

B. Shows no containers because detached mode hides them

C. Shows an error because -d is not valid with nginx

D. Shows the running nginx container with its container ID and status

Solution

1. Step 1: Understand docker run -d nginx

   This command runs the nginx container in detached mode, so it runs in the background.

2. Step 2: Understand docker ps output

   The docker ps command lists all running containers, including those running detached. It will show the nginx container with its ID, image, and status.

3. Final Answer:

   Shows the running nginx container with its container ID and status -> Option D

4. Quick Check:

   docker ps lists running containers including detached [OK]

Hint: docker ps always lists running containers, detached or not [OK]

Common Mistakes:

• Thinking detached containers are hidden from docker ps
• Confusing docker ps with docker logs
• Assuming -d causes errors with nginx image

4. You ran docker run -d nginx but the container stopped immediately. What is the most likely reason?

medium

A. The -d flag is invalid and caused the container to stop

B. You forgot to add the -it flag for interactive mode

C. The nginx container exited because it has no foreground process

D. Docker daemon is not running

Solution

1. Step 1: Understand container lifecycle with detached mode

   Detached mode runs containers in background, but if the main process exits immediately, the container stops.

2. Step 2: Analyze nginx container behavior

   Some nginx images may exit if no foreground process runs. This causes the container to stop right after starting.

3. Final Answer:

   The nginx container exited because it has no foreground process -> Option C

4. Quick Check:

   Container stops if main process exits immediately [OK]

Hint: Detached mode won't keep container alive if main process ends [OK]

Common Mistakes:

• Assuming -d flag causes errors
• Confusing interactive mode with container lifecycle
• Not checking if Docker daemon is running

5. You want to run a container in detached mode and later check its logs. Which sequence of commands is correct?

hard

A. docker run -d --name myapp nginx; docker logs myapp

B. docker run --name myapp nginx -d; docker stop myapp

C. docker run -it --name myapp nginx; docker logs myapp

D. docker run -d nginx; docker attach myapp

Solution

1. Step 1: Run container in detached mode with a name

   Use docker run -d --name myapp nginx to start the container in background with a name for easy reference.

2. Step 2: Check logs of the running container

   Use docker logs myapp to view the logs of the named container without attaching to it.

3. Final Answer:

   docker run -d --name myapp nginx; docker logs myapp -> Option A

4. Quick Check:

   Detached run + named container + logs command [OK]

Hint: Name containers to easily check logs after detached run [OK]

Common Mistakes:

• Using -it instead of -d for detached mode
• Trying to attach instead of using logs to view output
• Placing -d after image name