Official Nginx Docker image - Step-by-Step Execution

Process Flow - Official Nginx Docker image

Pull nginx image from Docker Hub

↓

Create container from image

↓

Start nginx server inside container

↓

Access nginx via mapped port

↓

Stop and remove container when done

This flow shows how the official nginx Docker image is pulled, run as a container, and accessed via a port mapping.

Execution Sample

Nginx

docker pull nginx

docker run --name mynginx -p 8080:80 -d nginx

docker ps

curl http://localhost:8080

Pulls the nginx image, runs a container mapping port 8080 to 80, lists running containers, and fetches the nginx welcome page.

Process Table

Step	Command	Action	Result/Output
1	docker pull nginx	Download nginx image from Docker Hub	Status: Downloaded newer image for nginx:latest
2	docker run --name mynginx -p 8080:80 -d nginx	Create and start container named mynginx	Container ID printed, nginx server running inside container
3	docker ps	List running containers	Shows mynginx container with port 8080->80 mapping
4	curl http://localhost:8080	Request nginx welcome page	HTML content of nginx default welcome page
5	docker stop mynginx	Stop the running container	mynginx stopped
6	docker rm mynginx	Remove the stopped container	mynginx removed

💡 Container stopped and removed, nginx server no longer running

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6
nginx image	Not present	Downloaded	Available locally	Available locally	Available locally	Available locally	Available locally
mynginx container	Not created	Not created	Running	Running	Running	Stopped	Removed
Port mapping	None	None	8080->80 active	8080->80 active	8080->80 active	None	None

Key Moments - 3 Insights

Why do we map port 8080 to 80 in the docker run command?

Port 80 is the default nginx port inside the container. Mapping it to 8080 on the host lets us access nginx via localhost:8080 without needing root privileges.

What happens if we run docker run without -d option?

Without -d (detached), the container runs in the foreground and logs appear in the terminal, blocking further commands until stopped (see step 2 in execution_table).

Why do we need to stop and remove the container?

Stopping frees system resources; removing deletes the container instance so it doesn't clutter your system (steps 5 and 6).

Visual Quiz - 3 Questions

Look at the execution table, what is the output of the 'docker ps' command at step 3?

A Shows the nginx image downloaded

B Shows no containers running

C Shows the running mynginx container with port 8080->80 mapping

D Shows the container stopped

💡 Hint

Check the 'Result/Output' column for step 3 in the execution_table

At which step does the nginx server start running inside the container?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look at the 'Action' and 'Result/Output' columns for step 2 in the execution_table

If you omit the '-p 8080:80' option in the docker run command, what changes in the variable_tracker?

A Port mapping remains None after step 2

B Port mapping shows 8080->80 active after step 2

C Container will not run

D Image will not download

💡 Hint

Check the 'Port mapping' row in variable_tracker after step 2

Concept Snapshot

Official Nginx Docker image usage:
- Pull image: docker pull nginx
- Run container: docker run --name mynginx -p 8080:80 -d nginx
- Access nginx at localhost:8080
- Stop container: docker stop mynginx
- Remove container: docker rm mynginx
Port mapping connects container port 80 to host port 8080.

Full Transcript

This visual execution shows how to use the official nginx Docker image. First, the image is pulled from Docker Hub. Then a container named mynginx is created and started with port 8080 on the host mapped to port 80 inside the container where nginx listens. The running containers are listed to confirm. Accessing http://localhost:8080 returns the nginx welcome page. Finally, the container is stopped and removed to clean up. Variables like the image presence, container state, and port mapping change step-by-step as shown. Key points include why port mapping is needed and the effect of running detached. The quiz tests understanding of these steps and their outputs.

Practice

1. What is the primary purpose of the official Nginx Docker image?

easy

A. To quickly run Nginx inside a container for web serving

B. To build custom Linux kernels

C. To manage databases inside containers

D. To create virtual machines

Solution

1. Step 1: Understand the role of Nginx

   Nginx is a web server used to serve websites and handle web traffic.

2. Step 2: Recognize the Docker image purpose

   The official Nginx Docker image allows running Nginx easily inside containers for web serving.

3. Final Answer:

   To quickly run Nginx inside a container for web serving -> Option A

4. Quick Check:

   Official Nginx Docker image = Quick Nginx container [OK]

Hint: Nginx image runs web server in container fast [OK]

Common Mistakes:

• Confusing Nginx with database or VM tools
• Thinking it builds Linux kernels
• Assuming it manages virtual machines

2. Which Docker command correctly runs the official Nginx image exposing port 80 on the host?

easy

A. docker run -p 80 nginx

B. docker run -p 8080:80 nginx

C. docker run -p 80:80 nginx

D. docker run nginx -p 80:80

Solution

1. Step 1: Understand Docker port mapping syntax

   The correct syntax is docker run -p hostPort:containerPort image.

2. Step 2: Match the command to expose port 80 on host

   docker run -p 80:80 nginx uses -p 80:80 which maps host port 80 to container port 80 correctly.

3. Final Answer:

   docker run -p 80:80 nginx -> Option C

4. Quick Check:

   Port mapping syntax = -p hostPort:containerPort [OK]

Hint: Use -p hostPort:containerPort to expose ports [OK]

Common Mistakes:

• Omitting container port in -p option
• Placing -p after image name
• Using wrong port numbers

3. What will be the result of running this command?

docker run --rm -p 8080:80 nginx

Then accessing http://localhost:8080 in a browser?

medium

A. Connection refused error

B. You will see the default Nginx welcome page

C. 404 Not Found error

D. Docker container will fail to start

Solution

1. Step 1: Analyze the Docker run command

   The command runs Nginx container mapping host port 8080 to container port 80, with --rm to remove container after exit.

2. Step 2: Understand Nginx default behavior

   Nginx serves a default welcome page on port 80 if no custom config is provided.

3. Final Answer:

   You will see the default Nginx welcome page -> Option B

4. Quick Check:

   Default Nginx page served on mapped port [OK]

Hint: Default Nginx page shows if no config mounted [OK]

Common Mistakes:

• Expecting 404 without custom config
• Thinking container fails without volumes
• Confusing port 80 with 8080 inside container

4. You tried to run:

docker run -p 80:80 nginx

but got an error: port is already allocated. What is the best fix?

medium

A. Stop the process using port 80 or use a different host port

B. Change the container port to 8080

C. Remove the Nginx image and pull again

D. Run the container without port mapping

Solution

1. Step 1: Understand the error meaning

   "port is already allocated" means host port 80 is in use by another process.

2. Step 2: Choose a fix for port conflict

   Stopping the process using port 80 or mapping to a different host port avoids conflict.

3. Final Answer:

   Stop the process using port 80 or use a different host port -> Option A

4. Quick Check:

   Port conflict fix = stop process or change host port [OK]

Hint: Port conflict means host port busy; change or free it [OK]

Common Mistakes:

• Changing container port instead of host port
• Deleting image won't fix port conflict
• Running without port mapping disables access

5. You want to customize Nginx by using your own nginx.conf file located at /home/user/nginx.conf. Which Docker command correctly mounts this config into the container?

hard

A. docker run -v /etc/nginx/nginx.conf:/home/user/nginx.conf -p 8080:80 nginx

B. docker run -v /home/user/nginx.conf:/usr/local/nginx/nginx.conf -p 8080:80 nginx

C. docker run -v /home/user/nginx.conf:/etc/nginx/conf.d/nginx.conf -p 8080:80 nginx

D. docker run -v /home/user/nginx.conf:/etc/nginx/nginx.conf:ro -p 8080:80 nginx

Solution

1. Step 1: Identify correct Nginx config path inside container

   The main config file path in official Nginx image is /etc/nginx/nginx.conf.

2. Step 2: Use volume mount syntax to map host config

   Mount host file /home/user/nginx.conf to container path /etc/nginx/nginx.conf with read-only flag :ro.

3. Final Answer:

   docker run -v /home/user/nginx.conf:/etc/nginx/nginx.conf:ro -p 8080:80 nginx -> Option D

4. Quick Check:

   Mount host config to /etc/nginx/nginx.conf with :ro [OK]

Hint: Mount config to /etc/nginx/nginx.conf with :ro for safety [OK]

Common Mistakes:

• Reversing source and target paths in -v option
• Mounting to wrong container config directory
• Omitting :ro to prevent accidental changes