📖 Scenario: You want to run a simple web server inside a Docker container on your computer. This will help you understand how to start containers using the docker run command.
🎯 Goal: Learn how to run a Docker container using the docker run command with specific options to start a web server and expose it to your computer.
📋 What You'll Learn
Use the official nginx Docker image
Run the container in detached mode
Map port 8080 on your computer to port 80 in the container
Name the container mynginx
💡 Why This Matters
🌍 Real World
Running containers is how many developers and system administrators deploy applications quickly and consistently on any machine.
💼 Career
Knowing how to use <code>docker run</code> is a fundamental skill for DevOps roles, cloud engineers, and software developers working with containerized applications.
Progress0 / 4 steps
1
Pull the nginx image
Write the docker pull nginx command to download the official nginx image from Docker Hub.
Docker
Hint
Use docker pull nginx to get the image from Docker Hub.
2
Run nginx container in detached mode
Write the docker run command to start a container named mynginx from the nginx image in detached mode.
Docker
Hint
Use docker run --name mynginx -d nginx to start the container in the background.
3
Map port 8080 to port 80
Modify the docker run command to map port 8080 on your computer to port 80 inside the container.
Docker
Hint
Add -p 8080:80 to map ports.
4
Verify the container is running
Write the docker ps command to list running containers and verify mynginx is running.
Docker
Hint
Use docker ps to see running containers.
Practice
(1/5)
1. What does the docker run command do?
easy
A. Starts a new container from a specified image
B. Builds a new Docker image from a Dockerfile
C. Stops a running Docker container
D. Deletes an existing Docker image
Solution
Step 1: Understand the purpose of docker run
The docker run command is used to start a new container based on a Docker image.
Step 2: Differentiate from other Docker commands
Commands like docker build create images, docker stop stops containers, and docker rmi removes images, so they are not correct here.
Final Answer:
Starts a new container from a specified image -> Option A
Quick Check:
docker run = start container [OK]
Hint: Remember: run = start container from image [OK]
Common Mistakes:
Confusing 'run' with 'build' command
Thinking 'run' deletes images
Mixing 'run' with stopping containers
2. Which of the following is the correct syntax to run an interactive container with a bash shell using the image ubuntu?
easy
A. docker run ubuntu -it bash
B. docker run -d ubuntu bash
C. docker run -it ubuntu bash
D. docker run ubuntu -d -it bash
Solution
Step 1: Identify flags for interactive mode
The -it flag is used to run a container interactively with a terminal attached.
Step 2: Check command order and flags
The correct syntax places flags immediately after docker run, then the image name, then the command to run inside the container.
Final Answer:
docker run -it ubuntu bash -> Option C
Quick Check:
Flags before image, -it for interactive [OK]
Hint: Put flags right after 'docker run', then image, then command [OK]
Common Mistakes:
Placing flags after image name
Using -d for interactive shell
Mixing order of command and flags
3. What will be the output of the following command?
docker run --rm alpine echo Hello World
medium
A. Hello World
B. Container ID printed
C. Error: alpine image not found
D. No output, container runs in background
Solution
Step 1: Understand the command components
docker run --rm alpine echo Hello World runs the echo Hello World command inside an Alpine container and removes the container after it finishes.
Step 2: Predict the output
The command prints Hello World to the terminal, then the container stops and is removed automatically.
Final Answer:
Hello World -> Option A
Quick Check:
Run with echo prints text, --rm cleans up [OK]
Hint: Echo prints text, --rm removes container after run [OK]
Common Mistakes:
Expecting container ID output
Thinking container stays running
Assuming image is missing
4. You run docker run -p 8080:80 nginx but cannot access the web server on port 8080. What is a likely cause?
medium
A. Port mapping syntax is incorrect
B. The container is not running
C. You forgot to add -d to run detached
D. Port 80 inside container is not exposed
Solution
Step 1: Check container running status
If the container is not running, port mapping won't work and you can't access the server.
Step 2: Verify port exposure and syntax
By default, nginx listens on port 80 and the syntax -p 8080:80 is correct. -d is optional but recommended for background.
Final Answer:
The container is not running -> Option B
Quick Check:
Container must run for port mapping to work [OK]
Hint: Check if container is running before checking ports [OK]
Common Mistakes:
Assuming port 80 is not exposed by nginx
Thinking -d is required for port mapping
Misunderstanding port mapping syntax
5. You want to run a container from the image myapp that needs environment variables API_KEY and DEBUG set, and expose port 5000 on the host to port 80 in the container. Which command is correct?
hard
A. docker run -e API_KEY=123 DEBUG=true -p 5000:80 myapp
B. docker run -p 80:5000 -e API_KEY=123 -e DEBUG=true myapp
C. docker run myapp -e API_KEY=123 -e DEBUG=true -p 5000:80
D. docker run -e API_KEY=123 -e DEBUG=true -p 5000:80 myapp
Solution
Step 1: Set environment variables correctly
Use -e VAR=value for each environment variable before the image name.
Step 2: Map ports correctly
Host port 5000 maps to container port 80 with -p 5000:80. The order is flags, then image name.
Step 3: Verify command order and syntax
Options must come before the image name. docker run -p 80:5000 -e API_KEY=123 -e DEBUG=true myapp reverses ports, C places options after image, D misses -e for second variable.
Final Answer:
docker run -e API_KEY=123 -e DEBUG=true -p 5000:80 myapp -> Option D
Quick Check:
Flags before image, correct port and env syntax [OK]
Hint: Put all flags before image; use -e for each env var [OK]
Common Mistakes:
Placing options after image name
Reversing port mapping order
Missing -e for environment variables
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.