Custom config in Docker in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Docker command?

You run this command to start an nginx container with a custom config file mounted. What will be the output of docker ps immediately after?

Nginx

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

A No container is created

B Error: Cannot mount /home/user/nginx.conf because it does not exist

C Container exits immediately due to config error

D A running container named 'mynginx' listening on port 8080

💡 Hint

Check if the config file path is correct and the container runs detached.

The command runs nginx detached with a custom config file mounted read-only. If the file exists and is valid, the container runs and listens on port 8080.

❓ Configuration

intermediate

Which Dockerfile snippet correctly copies a custom nginx config?

You want to build a Docker image that uses your custom nginx.conf file inside the container at /etc/nginx/nginx.conf. Which snippet is correct?

A ADD /etc/nginx/nginx.conf nginx.conf

B COPY nginx.conf /etc/nginx/nginx.conf

C COPY /etc/nginx/nginx.conf nginx.conf

D ADD nginx.conf /usr/local/nginx/nginx.conf

💡 Hint

COPY copies from build context to container path.

COPY copies the local file nginx.conf to the container path /etc/nginx/nginx.conf. ADD syntax is similar but less preferred here.

❓ Troubleshoot

advanced

Why does nginx fail to start with this Docker volume mount?

You run:
docker run -d -v /home/user/nginx.conf:/etc/nginx/nginx.conf nginx
But the container exits immediately. What is the most likely cause?

A The host file /home/user/nginx.conf has wrong permissions or is empty

B The container image does not have nginx installed

C The port 80 is already in use on the host

D Docker daemon is not running

💡 Hint

Check the config file content and permissions on the host.

If the config file is empty or unreadable, nginx fails to start and container exits immediately.

🔀 Workflow

advanced

What is the correct workflow to update nginx config in a running container?

You have a running nginx container with a custom config mounted from the host. You want to update the config and apply changes without restarting the container. What should you do?

A Edit the config file on the host and send nginx reload signal inside the container

B Stop the container, replace the config file inside container, then start it

C Rebuild the image with new config and redeploy container

D Edit the config file inside the container directly using docker exec

💡 Hint

Think about how volume mounts reflect changes and how nginx reload works.

Editing the host file updates the mounted config immediately. Sending nginx reload signal applies changes without downtime.

✅ Best Practice

expert

Which approach is best for managing multiple custom nginx configs in Docker for different environments?

You have dev, staging, and production environments each needing different nginx configs. Which is the best Docker setup?

A Build separate Docker images each with its own config baked in

B Use environment variables inside nginx.conf to switch configs dynamically

C Use one image and mount different config files at runtime per environment

D Copy all configs inside one image and switch config by editing container files

💡 Hint

Consider flexibility and image rebuild overhead.

Mounting different config files at runtime allows one image to be reused across environments without rebuilding.

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