Volume mounting for configs in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Nginx container with volume mount for custom config

You run this Docker command to start an nginx container with a custom config file mounted:

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

What will be the effect of the -v option here?

A It mounts the host directory <code>/home/user/nginx.conf</code> as a volume inside the container at <code>/etc/nginx/nginx.conf</code>.

B It copies the host file <code>/home/user/nginx.conf</code> into the container's <code>/etc/nginx/nginx.conf</code> and allows writing inside the container.

C It mounts the host file <code>/home/user/nginx.conf</code> as the container's <code>/etc/nginx/nginx.conf</code> file in read-only mode.

D It creates a new empty file <code>/etc/nginx/nginx.conf</code> inside the container and ignores the host file.

💡 Hint

Look at the -v syntax: host_path:container_path:mode.

The -v option mounts a host file or directory into the container. Here, a single file /home/user/nginx.conf is mounted as /etc/nginx/nginx.conf inside the container. The :ro means read-only.

🧠 Conceptual

intermediate

Purpose of volume mounting config files in nginx container

Why do we mount configuration files from the host into an nginx container instead of baking them into the image?

A Because nginx containers cannot run without volume mounts.

B To allow easy updates to configs without rebuilding the image or restarting the container.

C To increase container startup time by loading configs externally.

D To prevent nginx from reading any configuration at all.

💡 Hint

Think about how you update settings in real life without changing the whole product.

Mounting config files allows changing nginx settings by editing files on the host. This avoids rebuilding the container image and makes updates faster and simpler.

❓ Configuration

advanced

Correct Docker Compose volume syntax for nginx config

Which Docker Compose snippet correctly mounts a custom nginx config file ./nginx.conf from the project directory into the container at /etc/nginx/nginx.conf as read-only?

Nginx

services:
  web:
    image: nginx
    ports:
      - "8080:80"
    volumes:

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

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

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

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

💡 Hint

Remember the format is host_path:container_path:mode.

Option D correctly mounts the host file ./nginx.conf to the container path with read-only mode. Option D misses the read-only flag. Option D reverses paths. Option D sets read-write mode.

❓ Troubleshoot

advanced

Nginx container ignores mounted config file changes

You mounted a custom nginx config file into a running container. After editing the host config file, nginx inside the container does not reflect the changes. What is the most likely cause?

A Nginx needs to be reloaded or restarted inside the container to apply config changes.

B Docker does not support mounting files, only directories.

C The volume mount is read-only, so changes are blocked.

D The container automatically reloads configs every 5 minutes, so wait longer.

💡 Hint

Think about how software applies config changes after editing files.

Editing the config file on the host updates the file inside the container, but nginx must reload or restart to read the new config. Without reload, nginx keeps using the old settings.

✅ Best Practice

expert

Secure volume mounting of nginx configs in production

In a production environment, what is the best practice to securely mount nginx configuration files into containers?

A Mount config files as read-only volumes and restrict host file permissions to trusted users only.

B Mount config files as read-write volumes so containers can modify configs dynamically.

C Bake configs into the container image and avoid volume mounts entirely.

D Use anonymous volumes without specifying host paths to prevent host access.

💡 Hint

Consider security and immutability principles for production.

Mounting config files as read-only prevents accidental or malicious changes from inside the container. Restricting host file permissions protects configs from unauthorized edits. Baking configs into images reduces flexibility. Anonymous volumes do not provide config control.