NGINX With Docker: Beginner’s Guide To Dockerize NGINX Server

If you’re reading this, you’re probably diving into the world of NGINX and Docker for the first time. Maybe you’re a developer, a DevOps newbie, or just someone curious about how to make your web server setup easier. Trust me, I’ve been there. The first time I tried to set up NGINX with Docker, I felt like I was trying to solve a Rubik’s Cube blindfolded.

But don’t worry—I’ve got your back. By the end of this guide, you’ll have a working NGINX setup inside Docker, and you’ll understand why this combo is such a game-changer.

NGINX And Docker

What is NGINX?

NGINX is a powerful web server and reverse proxy. It’s like the Swiss Army knife of web servers—it can handle static content, load balancing, SSL termination, and more.

What is Docker?

Docker, on the other hand, is a containerization platform that lets you package applications and their dependencies into lightweight, portable containers. Think of it as a lunchbox for your software—everything you need is neatly packed and ready to go.

Now, When you combine NGINX with Docker, you get a setup that’s easy to deploy, scalable, and consistent across different environments. No more “it works on my machine” excuses!

Why Use NGINX With Docker?

Docker simplifies NGINX deployment, scaling, and management across environments.

I remember the first time I tried to install NGINX directly on my server. It worked, but then I had to deal with dependency issues, conflicting versions, and the dreaded “port is already in use” error. Docker solves all of that.

Here’s why Dockerizing your NGINX server is a great idea:

• Scalability: Need more NGINX instances? Just fire up more containers.
• Consistency: Your NGINX setup will work the same way on your laptop, your colleague’s machine, and your production server.
• Isolation: No more worrying about conflicting software versions. Docker containers are self-contained.
• Ease of Deployment: Spin up a new NGINX instance in seconds.

How to setup NGINX with Docker?

Before we dive in, make sure you have:

• Basic command line knowledge
• A text editor you’re comfortable with
• About 30 minutes of free time

Step 1: Install Docker

If you don’t have Docker installed, head over to the official Docker website and follow the installation instructions for your operating system. Once installed, verify it’s working by running:

docker --version

You should see something like Docker version 20.10.17.

Step 2: Pull the NGINX Docker Image

Docker makes it easy to use pre-built images. To pull the official NGINX image, run:

docker pull nginx

This downloads the latest NginX image from Docker Hub.

Step 3: Run NGINX in a Docker Container

Now, let’s start an NginX container:

docker run --name my-nginx -d -p 80:80 nginxCode language: CSS (css)

Here’s what this command does:

• --name my-nginx: Names the container “my-nginx.”
• -d: Runs the container in detached mode (in the background).
• -p 80:80: Maps port 80 on your host machine to port 80 in the container.

Open your browser and navigate to http://localhost. You should see the default NGINX welcome page. Congrats, you’ve just run NGINX in Docker!

Step 4: Customize NGINX Configuration

The default NginX setup is great, but you’ll probably want to customize it. Let’s create a custom configuration file.

1. Create a directory for your NginX config:

mkdir -p ~/my-nginx-config

2. Create a file named default.conf inside this directory:

nano ~/my-nginx-config/default.confCode language: JavaScript (javascript)

Add the following basic configuration:

server {
    listen 80;
    server_name localhost;

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

3. Run the NginX container with your custom config:

docker run --name my-nginx -d -p 80:80 -v ~/my-nginx-config:/etc/nginx/conf.d nginxCode language: JavaScript (javascript)

The -v flag mounts your local config directory into the container.

Step 5 (Optional): Dockerize NGINX with docker compose

While compose is not mandatory for this simple tutorial use case, it still can make your life easier by not having to deal with lengthy command-line arguments, etc. For multi-container use cases, it’s a must, though.

Let’s create a basic docker-compose.yml file. This is where I made my first mistake years ago – trying to configure everything directly in the container instead of using volume mounts!

version: '3'
services:
  nginx:
    image: nginx:latest
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./my-nginx-config:/etc/nginx/conf.d
      - /usr/nginx/html:/var/www/htmlCode language: JavaScript (javascript)

Now run the command as follows:

docker compose up

Setup SSL/TLS For Dockerized NGINX

Securing your site with HTTPS is a must. Let’s Encrypt provides free SSL certificates, and NGINX makes it easy to integrate them. While setting up SSL for NGINX, especially with Docker might sound a bit daunting at first, its not too hard.

Note: You should always set up the SSL certbot on the host machine instead of the container, as containers are not permanent. Use the docker volume mount to hook them up nicely afterward.

1. Install Certbot (Let’s Encrypt client):

sudo apt-get install certbotCode language: JavaScript (javascript)

2. Obtain an SSL certificate:

sudo certbot certonly --standalone -d yourdomain.comCode language: CSS (css)

3. Update your NginX config to use the SSL certificate:

server {
    listen 443 ssl;
    server_name yourdomain.com;

    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;

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

3. NGINX Configuration

Create a file nginx/conf.d/default.conf:

server {
    listen 80;
    server_name yourdomain.com;
    
    location /.well-known/acme-challenge/ {
        root /var/www/certbot;
    }

    location / {
        return 301 https://$host$request_uri;
    }
}

server {
    listen 443 ssl;
    server_name yourdomain.com;
    
    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;
    
    # Improved SSL configuration
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers HIGH:!aNULL:!MD5;
    
    location / {
        root /var/www/html;
        index index.html;
    }
}Code language: PHP (php)

And lastly, make sure the docker-compose file also properly has the volume mount setup for the SSL certificates from the host os to the docker OS.

services:
  nginx:
    image: nginx:latest
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./my-nginx-config:/etc/nginx/conf.d
      - /etc/letsencrypt/live/yourdomain.com:/etc/letsencrypt/live/yourdomain.com 
      - /usr/nginx/html:/var/www/htmlCode language: JavaScript (javascript)

Common Issues

Permission Issues: Docker containers run as root by default, but files created by Certbot might have different permissions. Fix this with:

chmod -R 755 ./certbot

Certificate Renewal: Don’t forget to set up auto-renewal! Add this to your crontab:

0 12 * * * docker-compose run certbot renew && docker-compose restart nginx

Pro Tips

• Always Use Volume Mounts: This makes it easy to update configurations without rebuilding containers. And as mentioned above, is a must if you are doing SSL configuration.
• Test Locally First: Use self-signed certificates for local development. (example with openssl)
• Monitor Your Logs: NGINX logs can be gold when debugging issues:

docker-compose logs -f nginx

Real-world Use Cases

A NGINX server within Dockerized environment is perfect for:

• Hosting static websites: Serve HTML, CSS, and JavaScript files effortlessly.
• Reverse proxying: Route traffic to multiple backend services.
• Load balancing: Distribute traffic across multiple servers.
• SSL: Secure your site with HTTPS for free using Let’sEncrypt.

I’ve used this setup for everything from personal blogs to production-grade microservices. It’s versatile, reliable, and—once you get the hang of it—super easy to manage.

Limitations and Things to Watch Out For

• Docker containers add a small overhead compared to bare metal installations
• SSL certificate renewal needs to be properly scheduled(as shown above)
• Container updates need to be managed carefully

Final Thoughts

Setting up NGINX with Docker might seem scary at first, but trust me – once you get the hang of it, you’ll never want to go back to traditional setups. I still remember the satisfaction of getting my first containerized NGINX server running with valid SSL certificates. It’s like building with LEGO blocks – once you understand how the pieces fit together, the possibilities are endless!

Remember, everyone starts somewhere. Don’t get discouraged if things don’t work perfectly the first time. Keep experimenting, and feel free to reach out to the community – we’ve all been there!

Happy containerizing! 🐳