Modern DevOps
Docker &
nginx
Why "it works on my machine" killed careers. What containers actually are. And how nginx quietly powers a third of the internet.
Sections
7
Read time
25 min
Level
Beginner
Without Docker:
Dev: Python 3.11 ✓
Server: Python 3.8 ← different!
App crashes 💥
With Docker:
docker run myapp ← one command
Your Mac ✓
Server ✓
AWS cloud ✓ identical everywhere
The Problem Docker Solves
Every developer has said this at least once. You build an app on your Mac, it works perfectly. You send it to a colleague or deploy it to a server — and it immediately crashes.
Your Mac 💻
Python 3.11 ✓
Library A version 2.0 ✓
Library B version 5.1 ✓
App works perfectly ✓
Your server 🖥️
Python 3.8 ← different version!
Library A version 1.5 ← old version!
Library B not installed ← missing!
App crashes 💥
“It works on my machine!”
— every developer, at least once
Docker solves this completely by packaging your app and everything it needs into a single portable box called a container.
Key Takeaway
Docker doesn't fix your code — it eliminates environment differences. Same container, same behavior, everywhere.
What is Docker?
Docker packages your app and all its dependencies into a container — a self-contained box that runs identically on any machine.
What's inside a container:
┌─────────────────────────────┐
│ CONTAINER │
│ │
│ Your app │
│ Python 3.11 │
│ Library A 2.0 │
│ Library B 5.1 │
│ All config files │
│ │
└─────────────────────────────┘
Your Mac → runs ✓
Friend's PC → runs ✓
Ubuntu server → runs ✓
AWS cloud → runs ✓
Where Docker Hub comes in
Docker Hub is like GitHub but for Docker images. Thousands of ready-made images you can use instantly:
ubuntuBare Ubuntu system
nginxWeb server, ready
postgresFull PostgreSQL DB
pythonPython + pip
nodeNode.js ready
redisCache DB
mysqlMySQL database
alpineTiny Linux base
Containers vs Virtual Machines
You already use a VM (your Ubuntu server). How is a Docker container different?
Virtual Machine
A full house with its own kitchen
Your Mac hardware
└── UTM (hypervisor)
└── Full Ubuntu OS
├── kernel, drivers
└── your app
Heavy — full OS inside
Minutes to start, GBs of RAM
Docker Container
A hotel room — shared building
Ubuntu Server
Linux kernel (shared ↔ all containers)
├── Container A: App + libs
├── Container B: App + libs
└── Container C: App + libs
Light — no separate OS
Seconds to start, MBs of RAM
Container = a hotel room (shared building infrastructure — electricity, plumbing, elevator — your own private space inside)
Hotel rooms are faster to set up, cheaper, and you can have 100 of them in one building.
Did You Know?
Images, Containers & Dockerfile
Image
A blueprint — like a recipe. Static, read-only. Stored on Docker Hub. From one image you can create 100 identical containers.
Container
A running instance made from an image. Like a meal made from a recipe. You can run, stop, restart, delete containers independently.
Dockerfile
A text file with instructions to build your OWN custom image. Define what OS to start from, what software to install, what files to copy in.
A real Dockerfile
Dockerfile
Key Takeaway
Image = recipe. Container = meal. Dockerfile = instructions for writing your own recipe. One image, infinite identical containers.
Docker Commands
The commands you'll use 90% of the time:
docker pull ubuntuDownload the Ubuntu image from Docker Hub
docker run ubuntuCreate and start a container from the ubuntu image
docker run -it ubuntu bash-it = interactive terminal. Drops you inside the container with a bash shell
docker run -d nginx-d = detached (runs in background). Start nginx web server in background
docker psList all currently running containers
docker ps -aList ALL containers, including stopped ones
docker stop <id>Stop a running container (graceful shutdown)
docker rm <id>Delete a stopped container
docker imagesList all images downloaded on your machine
docker logs <id>See stdout/stderr output from a container
Real-world example
❌ Without Docker
Server 1 → Python 3.8, app v1.0
Server 2 → Python 3.9, app v1.0 ← drift
Server 3 → Python 3.8, app v1.1 ← drift
Nightmare to manage. Every server different.
✅ With Docker
docker run myapp:v1.0 ← all servers
Identical everywhere, always.
Update → docker run myapp:v1.1
Rollback → docker run myapp:v1.0
What is nginx?
When you type a URL in your browser, something on the server receives your request and sends back the webpage. That "something" is a web server — and nginx is one of the most popular ones in the world.
You type google.com
↓
Your browser sends a request to the server
↓
nginx receives the request
↓
nginx finds the right file (HTML, image, etc)
↓
nginx sends it back to your browser
↓
You see the webpage ✓
Who uses nginx?
Did You Know?
nginx vs Apache
Apache (1995)
- • Each request gets its own thread
- • Gets slow under heavy traffic
- • More memory per connection
- • Easier config for beginners
nginx (2004)
- • Event-driven, non-blocking
- • Handles thousands of connections
- • Far less memory
- • Built for production scale
What nginx Can Do
nginx is far more than a web server. Here are the 4 main roles it plays in production:
Serve Static Files
HTML, CSS, images, JavaScript. User requests index.html → nginx finds it and sends it back. Extremely fast — nginx is optimized for this.
Reverse Proxy
Sits in front of your app. Receives all requests → forwards to your app → sends response back. Protects your app from direct internet exposure.
Load Balancer
Spreads traffic across multiple servers. Server 1 gets request 1, Server 2 gets request 2. No single server gets overwhelmed.
SSL Termination
Handles HTTPS encryption. Your app communicates in plain HTTP internally. nginx handles the security layer — the padlock in the browser.
Key Takeaway
nginx + Docker is one of the most common production setups in the world. nginx handles incoming traffic and SSL, Docker containers run the actual app. Understanding both makes you dangerous as a DevOps engineer.
Key Concepts Flashcards
Click any card to flip and reveal the definition.