Custom config in Docker in Nginx - Commands & Configuration

Introduction

Sometimes you want to change how a program inside a Docker container works by giving it your own settings. This helps you control the program without changing the container itself.

When you want to change the website settings served by nginx inside a Docker container.

When you need to add custom rules like redirects or security headers to nginx running in Docker.

When you want to test different nginx configurations without rebuilding the whole Docker image.

When you want to keep your configuration files separate from the Docker image for easier updates.

When you want to share the same Docker image but use different settings on different servers.

Config File - nginx.conf

nginx.conf

events {}
http {
    server {
        listen 80;
        server_name localhost;

        location / {
            root /usr/share/nginx/html;
            index index.html index.htm;
        }

        location /hello {
            add_header Content-Type text/plain;
            return 200 'Hello from custom config!';
        }
    }
}

This file tells nginx to listen on port 80 and serve files from the default html folder. It also adds a new path /hello that returns a simple text message. This shows how you can add custom behavior with your own config.

Commands

This command runs the official nginx container in the background and maps port 8080 on your computer to port 80 inside the container. It uses the default nginx settings.

Terminal

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

Expected Output

a1b2c3d4e5f67890123456789abcdef0123456789abcdef0123456789abcdef0

→

--name - Gives the container a name for easy reference

→

-d - Runs the container in the background

→

-p - Maps a port from host to container

This copies your custom nginx.conf file from your computer into the running container, replacing the default config with your custom one.

Terminal

docker cp nginx.conf my-nginx:/etc/nginx/nginx.conf

Expected Output

No output (command runs silently)

This tells nginx inside the container to reload its configuration without stopping the container. It applies your new settings immediately.

Terminal

docker exec my-nginx nginx -s reload

Expected Output

No output (command runs silently)

This command checks if your custom config works by requesting the /hello path from nginx running in Docker. It should return your custom message.

Terminal

curl -i http://localhost:8080/hello

Expected Output

HTTP/1.1 200 OK

Server: nginx/1.23.3

Date: Thu, 01 Jun 2023 12:00:00 GMT

Content-Type: text/plain

Content-Length: 24

Connection: keep-alive



Hello from custom config!

→

-i - Includes HTTP headers in the output

Key Concept

If you remember nothing else from this pattern, remember: you can change how a program inside Docker works by copying your own config file into the container and reloading it.

Common Mistakes

Not copying the config file into the container before reloading nginx.

Nginx keeps using the old config and your changes have no effect.

Always copy your custom config file into the container path before telling nginx to reload.

Reloading nginx without the config file being valid.

Nginx will fail to reload and keep the old config, or the container logs will show errors.

Check your config file syntax locally before copying, for example with 'nginx -t'.

Mapping the wrong port or forgetting to map ports when running the container.

You cannot access nginx from your computer because the ports are not connected.

Use '-p 8080:80' to map container port 80 to host port 8080 or another free port.

Summary

Run the nginx container with port mapping to access it from your computer.

Copy your custom nginx.conf file into the running container to replace default settings.

Reload nginx inside the container to apply your new configuration without restarting.

Test your custom config by requesting the new path you added.

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