Custom config in Docker in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of using a custom configuration file in a Docker container running nginx?

A custom configuration file allows you to change nginx settings like server names, ports, or root directories without modifying the container image itself.

beginner

How do you include a custom nginx config file in a Docker container?

You can mount the custom config file into the container using a volume with the -v option in docker run, for example: docker run -v /my/custom/nginx.conf:/etc/nginx/nginx.conf nginx

beginner

What is the default location of the nginx main configuration file inside the official nginx Docker container?

The default main configuration file is located at /etc/nginx/nginx.conf inside the container.

intermediate

Why is it better to use a volume mount for custom config instead of building a new Docker image?

Using a volume mount lets you change the config quickly without rebuilding the image. It keeps your workflow simple and flexible.

beginner

What command would you use to start an nginx container with a custom config file located at /home/user/nginx.conf on your host?

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

Where should you mount your custom nginx config file inside the container?

A /etc/nginx/nginx.conf

B /usr/local/nginx.conf

C /var/www/html/nginx.conf

D /home/nginx/nginx.conf

The official nginx Docker image uses /etc/nginx/nginx.conf as the main config file location.

What Docker option allows you to use your own config file without rebuilding the image?

A -d (detached mode)

B -v (volume mount)

C -p (port mapping)

D -e (environment variable)

The -v option mounts a file or directory from the host into the container, allowing custom configs.

If your custom config file has errors, what will happen when nginx starts in the container?

A The container will restart endlessly

B nginx will ignore errors and start normally

C Docker will automatically fix the config

D nginx will fail to start and show an error

nginx validates the config on start and will fail if there are syntax errors.

Which command maps port 8080 on your host to port 80 in the nginx container?

A -p 8080:80

B -p 80:8080

C -v 8080:80

D -e 8080=80

The -p option maps host port 8080 to container port 80.

Why add ':ro' at the end of a volume mount for the config file?

A To rename the file inside the container

B To make the file writable inside the container

C To make the file read-only inside the container

D To remove the file after container stops

Adding ':ro' makes the mounted file read-only, preventing accidental changes.

Explain how to use a custom nginx configuration file with Docker without rebuilding the image.

Think about how Docker volumes work and where nginx expects its config.

Describe the benefits of using a volume mount for nginx config in Docker compared to building a new image.

Consider how changing files on the host affects the container.

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