Introduction

Tired of manually setting up web servers? In this quick demo we’ll spin up a full Nginx container with a single Docker command and explain what each option does. No configuration files, no package installs – just pure container magic.

Step‑by‑Step: Running Nginx

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

• docker run – creates and starts a new container from an image.

• -d – runs the container in detached mode, so your terminal is free for other work.

• --name web – assigns a human‑readable identifier (web) that you can reference in later commands.

• -p 8080:80 – maps host port 8080 to container port 80, exposing Nginx’s default HTTP port to the outside world.

• nginx – the image name; Docker will automatically pull it from Docker Hub if it isn’t present locally.

When you execute the command Docker performs the following actions:

1. Checks the local image cache; pulls nginx:latest if missing.

2. Creates a thin read‑only layer for the container.

3. Starts the container in the background, binding the specified port.

Verifying the Container

docker ps -f name=web

The docker ps command lists running containers. The -f name=web filter limits output to containers whose name matches web. You should see something like:

CONTAINER ID   IMAGE     COMMAND                  CREATED          STATUS          PORTS                     NAMES
a1b2c3d4e5f6   nginx     "/docker-entrypoint.…"   5 seconds ago    Up 4 seconds    0.0.0.0:8080->80/tcp      web

Open a browser and navigate to http://localhost:8080 – you’ll be greeted by the default Nginx welcome page.

Best Practices & Common Pitfalls

1. Avoid Port Conflicts

Before mapping a host port, ensure it isn’t already in use:

sudo lsof -iTCP -sTCP:LISTEN -P | grep 8080

If the port is taken, choose another free port, e.g., -p 8081:80.

2. Use Meaningful Container Names

A descriptive name (web, frontend, api-gateway) makes subsequent docker stop, docker logs, and docker exec commands easier to read and maintain.

3. Clean Up Stopped Containers

Docker retains stopped containers, which can clutter docker ps -a. Remove them promptly:

docker stop web && docker rm web

You can chain the commands as shown to ensure the name becomes available for reuse.

4. Pin Image Versions

Relying on the latest tag can introduce unexpected changes. Prefer a specific tag, e.g., nginx:1.25-alpine:

docker run -d --name web -p 8080:80 nginx:1.25-alpine

This guarantees reproducibility across environments.

Next Steps: Inspect, Interact, and Persist

View Logs

docker logs web

Shows Nginx’s startup output and any request logs.

Exec into the Container

docker exec -it web sh

Drops you into an interactive shell inside the running container, letting you explore the filesystem or debug configuration files.

Mount a Volume for Persistent Content

If you want to serve custom HTML without baking a new image:

docker run -d --name web \
  -p 8080:80 \
  -v $(pwd)/site:/usr/share/nginx/html:ro \
  nginx:1.25-alpine

The -v flag mounts the local site directory into Nginx’s document root. The :ro suffix makes it read‑only, protecting the container from accidental writes.

Conclusion

Running Nginx with a single docker run command illustrates Docker’s core promise: fast, reproducible, and isolated environments. By mastering the flags, handling common pitfalls, and leveraging next‑step techniques like logs, exec, and volumes, you can turn a one‑liner into a robust development workflow.

Feel free to comment with your favorite Docker tricks or ask questions!