Docker Compose with Nginx - Commands & Configuration

Introduction

Running multiple services together can be tricky. Docker Compose helps you start and manage several containers at once. Using it with Nginx lets you easily set up a web server alongside other services.

When you want to run a web server and an app together on your computer without conflicts

When you need to quickly start Nginx with custom settings for testing

When you want to share your web server setup with teammates easily

When you want to keep your web server and app isolated but connected

When you want to stop and start your web server and app with one command

Config File - docker-compose.yml

docker-compose.yml

version: '3.8'
services:
  web:
    image: nginx:1.23.4
    ports:
      - "8080:80"
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf:ro

This file tells Docker Compose to run an Nginx container.

version sets the Compose file format.

services defines the containers to run. Here, web is the Nginx container.

image specifies the Nginx version to use.

ports maps port 8080 on your computer to port 80 in the container, so you can access the web server at http://localhost:8080.

volumes mounts your local nginx.conf file inside the container to customize Nginx settings.

Commands

This command starts the Nginx container in the background using the docker-compose.yml file. The -d flag means detached mode, so the terminal is free for other commands.

Terminal

docker-compose up -d

Expected Output

Creating network "default" with the default driver

Creating web ... done

→

-d - Run containers in the background (detached mode)

This command shows the status of containers started by Docker Compose. It helps verify that the Nginx container is running.

Terminal

docker-compose ps

Expected Output

    Name                  Command               State           Ports         

----------------------------------------------------------------------------

web            nginx -g 'daemon off;'          Up      0.0.0.0:8080->80/tcp

This command fetches the homepage served by Nginx on your local machine to check if the web server is working.

Terminal

curl http://localhost:8080

Expected Output

<!DOCTYPE html>

<html>

<head>

<title>Welcome to nginx!</title>

</head>

<body>

<h1>Welcome to nginx!</h1>

</body>

</html>

This command stops and removes the containers, network, and other resources created by Docker Compose. Use it to clean up when you are done.

Terminal

docker-compose down

Expected Output

Stopping web ... done

Removing web ... done

Removing network default

Key Concept

If you remember nothing else from this pattern, remember: Docker Compose lets you start and manage multiple containers together easily with one simple file.

Common Mistakes

Not mapping ports correctly in docker-compose.yml

If ports are not mapped, you cannot access Nginx from your computer browser.

Always map container port 80 to a free port on your computer, like 8080:80.

Forgetting to mount the nginx.conf file

Without mounting, Nginx uses default settings and ignores your custom configuration.

Use volumes to mount your local nginx.conf to /etc/nginx/nginx.conf inside the container.

Running docker-compose up without -d and closing the terminal

The containers stop when the terminal closes if not run in detached mode.

Use docker-compose up -d to run containers in the background.

Summary

Create a docker-compose.yml file to define the Nginx service with port mapping and config file mount.

Use 'docker-compose up -d' to start the Nginx container in the background.

Check running containers with 'docker-compose ps' and test Nginx with 'curl http://localhost:8080'.

Stop and remove containers with 'docker-compose down' when finished.

Practice

1. What is the main purpose of using Docker Compose with Nginx?

easy

A. To replace Nginx with a different web server

B. To run Nginx and other services together easily using a YAML file

C. To write Nginx configuration files in JSON format

D. To compile Nginx from source code automatically

Solution

1. Step 1: Understand Docker Compose role

   Docker Compose helps run multiple services together using a simple YAML file.

2. Step 2: Connect with Nginx usage

   Using Docker Compose with Nginx lets you start Nginx and other needed services easily.

3. Final Answer:

   To run Nginx and other services together easily using a YAML file -> Option B

4. Quick Check:

   Docker Compose + Nginx = easy multi-service setup [OK]

Hint: Docker Compose uses YAML to run multiple services together [OK]

Common Mistakes:

• Thinking Docker Compose changes Nginx config format
• Confusing Docker Compose with Nginx replacement
• Assuming Docker Compose compiles software

2. Which of the following is the correct way to expose port 80 of an Nginx container in a Docker Compose file?

easy

A. publish: 80

B. expose: 80:80

C. ports: - "80:80"

D. port: 80

Solution

1. Step 1: Recall Docker Compose port syntax

   To expose ports, use the 'ports' key with format "hostPort:containerPort" as a list item.

2. Step 2: Match correct syntax

   Only 'ports: - "80:80"' correctly exposes container port 80 to host port 80.

3. Final Answer:

   ports: - "80:80" -> Option C

4. Quick Check:

   Expose ports with 'ports: - "host:container"' [OK]

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

Common Mistakes:

• Using 'expose' with port mapping syntax
• Writing 'port' instead of 'ports'
• Using 'publish' which is invalid in Compose

3. Given this Docker Compose snippet, what will happen when you run docker-compose up?

services:
  web:
    image: nginx:latest
    ports:
      - "8080:80"
    volumes:
      - ./site-content:/usr/share/nginx/html:ro

medium

A. Nginx will serve files from /usr/share/nginx/html on port 80 only

B. Nginx will serve default content on port 80

C. Nginx will fail to start due to volume error

D. Nginx will serve files from ./site-content on port 8080

Solution

1. Step 1: Analyze port mapping

   Port 8080 on host maps to port 80 in container, so access via localhost:8080.

2. Step 2: Analyze volume mapping

   Local folder './site-content' is mounted read-only to Nginx's html folder, so custom files are served.

3. Final Answer:

   Nginx will serve files from ./site-content on port 8080 -> Option D

4. Quick Check:

   Port 8080 mapped and volume mounted = custom site served [OK]

Hint: Check ports and volumes to predict container behavior [OK]

Common Mistakes:

• Ignoring port mapping and assuming port 80
• Assuming volume mount fails without error
• Confusing container and host ports

4. You wrote this Docker Compose service for Nginx but after running docker-compose up the container starts but you cannot access Nginx on port 80:

services:
  nginx:
    image: nginx
    ports:
      - "80"
    volumes:
      - ./html:/usr/share/nginx/html

What is the likely cause?

medium

A. Port mapping "80" maps a random host port to container 80; should be "80:80"

B. Volume path './html' does not exist

C. Image name 'nginx' is invalid

D. Missing environment variables for Nginx

Solution

1. Step 1: Check port mapping syntax

   "80" is valid short syntax mapping random host port to container port 80; to bind host port 80 use "80:80".

2. Step 2: Confirm other parts

   Volume path and image name are valid; environment variables are optional for basic Nginx.

3. Final Answer:

   Port mapping "80" maps a random host port to container 80; should be "80:80" -> Option A

4. Quick Check:

   Port mapping must be "hostPort:containerPort" [OK]

Hint: Port mapping needs both host and container ports separated by colon [OK]

Common Mistakes:

• Using single port number without colon
• Assuming volume path error without checking
• Thinking image name 'nginx' is wrong

5. You want to run Nginx with Docker Compose and add a custom configuration file nginx.conf located in your project folder. Which Docker Compose volume setting correctly mounts this file to override the default Nginx config at /etc/nginx/nginx.conf?

hard

A. - ./nginx.conf:/etc/nginx/nginx.conf:ro

B. - ./nginx.conf:/usr/share/nginx/html/nginx.conf

C. - /etc/nginx/nginx.conf:./nginx.conf

D. - ./nginx.conf:/etc/nginx/conf.d/nginx.conf

Solution

1. Step 1: Identify correct Nginx config path

   The main Nginx config file is at /etc/nginx/nginx.conf inside the container.

2. Step 2: Match volume mount syntax

   Mount local nginx.conf to container path with read-only flag ':ro' to override default config safely.

3. Final Answer:

   - ./nginx.conf:/etc/nginx/nginx.conf:ro -> Option A

4. Quick Check:

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

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

Common Mistakes:

• Mounting to wrong container path
• Reversing source and target paths
• Omitting ':ro' for config files