Custom config in Docker in Nginx - Mini Project: Build & Apply

Custom config in Docker

📖 Scenario: You want to run a simple web server using nginx inside a Docker container. Instead of using the default settings, you want to provide your own custom configuration file to control how the server behaves.This is like setting up your own rules for how a coffee machine works instead of using the factory settings.

🎯 Goal: Build a Docker setup that uses a custom nginx.conf file to configure the nginx server inside a Docker container.You will create the custom config file, write a Dockerfile to use it, and then run the container to see your custom settings in action.

📋 What You'll Learn

Create a custom nginx.conf file with a simple server block

Write a Dockerfile that copies the custom config into the container

Use the official nginx image as the base

Run the container and verify the custom config is used

💡 Why This Matters

🌍 Real World

Customizing nginx configuration inside Docker containers is common when deploying web servers with specific rules or behaviors.

💼 Career

DevOps engineers often need to create Docker images with custom configurations to ensure applications run correctly in different environments.

1

Create the custom nginx.conf file

Create a file named nginx.conf with this exact content:

events {
    worker_connections 1024;
}
http {
    server {
        listen 8080;
        location / {
            return 200 'Hello from custom nginx config!';
        }
    }
}

Nginx

# Create the nginx.conf file with the custom server block
# Your code here

Hint

This file tells nginx to listen on port 8080 and respond with a simple message.

2

Write the Dockerfile to use the custom config

Create a file named Dockerfile with these exact lines:

FROM nginx:latest
COPY nginx.conf /etc/nginx/nginx.conf

Nginx

events {
    worker_connections 1024;
}
http {
    server {
        listen 8080;
        location / {
            return 200 'Hello from custom nginx config!';
        }
    }
}

# Create the Dockerfile with FROM and COPY commands
# Your code here

Hint

This Dockerfile uses the official nginx image and replaces the default config with your custom one.

3

Build and run the Docker container

Write these exact commands to build and run the Docker container:

docker build -t custom-nginx .
docker run -d -p 8080:8080 --name mynginx custom-nginx

Nginx

FROM nginx:latest
COPY nginx.conf /etc/nginx/nginx.conf

# Build the Docker image and run the container
# Your code here

Hint

These commands create the image and start the container mapping port 8080.

4

Verify the custom nginx config is working

Run this exact command to check the server response:

curl -s http://localhost:8080

It should output:

Hello from custom nginx config!

Nginx

docker build -t custom-nginx .
docker run -d -p 8080:8080 --name mynginx custom-nginx

# Run curl to verify the server response
# Your code here

Hint

This command asks the server for the homepage and shows your custom message.

Practice

1. What is the main purpose of using a custom nginx configuration file in a Docker container?

easy

A. To install new software packages in the container

B. To change the Docker image version

C. To control how nginx behaves inside the container

D. To update the operating system inside the container

Solution

1. Step 1: Understand nginx configuration role

   The nginx config file controls server behavior like ports, routes, and security.

2. Step 2: Relate config to Docker container

   Using a custom config lets you set nginx behavior inside the container environment.

3. Final Answer:

   To control how nginx behaves inside the container -> Option C

4. Quick Check:

   Custom config controls nginx behavior [OK]

Hint: Custom config changes nginx inside container, not Docker itself [OK]

Common Mistakes:

• Confusing Docker image version with nginx config
• Thinking config updates OS or installs software
• Assuming config changes Docker runtime

2. Which Docker command option is used to mount a custom nginx config file into the container?

easy

A. -v

B. -p

C. -e

D. -d

Solution

1. Step 1: Identify Docker option for mounting files

   The -v option mounts a file or directory from host to container.

2. Step 2: Confirm usage for nginx config

   Mounting the nginx config file uses -v to link host config to container path.

3. Final Answer:

   -v -> Option A

4. Quick Check:

   Mount config file with -v [OK]

Hint: Use -v to mount files or folders into containers [OK]

Common Mistakes:

• Using -p which is for port mapping
• Using -e which sets environment variables
• Using -d which runs container detached

3. Given this Docker run command:

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

What will happen when you access http://localhost:8080?

medium

A. nginx will use the custom config from /home/user/nginx.conf

B. nginx will use the default config inside the container

C. The container will fail to start due to missing config

D. Port 80 inside container is not exposed

Solution

1. Step 1: Analyze volume mount

   The command mounts host file /home/user/nginx.conf to container path /etc/nginx/nginx.conf as read-only.

2. Step 2: Analyze port mapping and nginx behavior

   Port 8080 on host maps to port 80 in container, nginx uses the mounted config file.

3. Final Answer:

   nginx will use the custom config from /home/user/nginx.conf -> Option A

4. Quick Check:

   Mounted config file is used by nginx [OK]

Hint: Mounted config overrides default inside container [OK]

Common Mistakes:

• Assuming default config is used despite mounting
• Thinking container fails without explicit start error
• Confusing port mapping direction

4. You run this command but nginx inside the container fails to start:

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

What is the most likely cause?

medium

A. The port 8080 is already in use on host

B. The nginx.conf file has syntax errors

C. The volume mount path is incorrect

D. The Docker image name is wrong

Solution

1. Step 1: Check common nginx start failure reasons

   nginx fails to start if config file has syntax errors or is missing.

2. Step 2: Analyze given command and symptoms

   Volume mount looks correct, port mapping is standard, image name is valid. Syntax errors in config are common cause.

3. Final Answer:

   The nginx.conf file has syntax errors -> Option B

4. Quick Check:

   Syntax errors cause nginx start failure [OK]

Hint: Always test nginx config syntax before running container [OK]

Common Mistakes:

• Blaming port conflict without error message
• Assuming volume mount path is wrong without checking
• Thinking image name is incorrect without error

5. You want to run nginx in Docker with a custom config file and ensure the container reloads nginx if the config changes on the host. Which approach is best?

hard

A. Mount the config file with -v and restart the container manually after changes

B. Use environment variables to pass config settings instead of a file

C. Copy the config file into the image during build and rebuild image on changes

D. Mount the config file with -v and use a file watcher inside container to reload nginx

Solution

1. Step 1: Understand config update needs

   To reload nginx on config changes without restarting container, nginx must reload config dynamically.

2. Step 2: Evaluate options for dynamic reload

   Mounting config with -v allows live changes. Using a file watcher inside container can trigger nginx reload on changes.

3. Step 3: Compare other options

   Manual restart is less efficient, copying config requires rebuild, env vars don't replace full config file.

4. Final Answer:

   Mount the config file with -v and use a file watcher inside container to reload nginx -> Option D

5. Quick Check:

   File watcher + mounted config enables live reload [OK]

Hint: Use mounted config plus watcher to reload nginx automatically [OK]

Common Mistakes:

• Rebuilding image for every config change
• Restarting container manually each time
• Trying to replace config with environment variables