🐳 What is Docker and Why Containers Over VMs

Understand what a container is, why Docker revolutionized software delivery, and why every DevOps team uses containers over traditional virtual machines.

🧒 Simple Explanation (ELI5)

Imagine you are a chef sending your recipe to restaurants worldwide. With VMs, you ship the entire kitchen — oven, fridge, counters, walls. With Docker, you ship just a lunchbox — your recipe, your exact ingredients, in a self-contained box that works in any kitchen.

Docker containers package your application and everything it needs (code, runtime, libraries, config) into a single, portable unit that runs identically on your laptop, a CI server, and production.

🔧 Technical Explanation

Containers vs Virtual Machines

Containers share the host OS kernel using Linux namespaces (process/network isolation) and cgroups (CPU/memory limits). There is no guest OS to boot — that is why containers start in milliseconds and use megabytes, while VMs need minutes and gigabytes.

Core Docker Objects

• Image — a read-only snapshot of your app + dependencies, stored as layers. Like a class in OOP.
• Container — a running instance of an image, with a writable layer. Like an object instantiated from a class.
• Dockerfile — a script that defines how to build an image, step by step.
• Registry — a storage service for images (Docker Hub, Azure Container Registry).
• Layer — each Dockerfile instruction adds a cached, reusable layer to the image.

💻 Essential Commands

# Pull an image from Docker Hub
docker pull nginx:latest

# Run a container (detached, port mapped, named)
docker run -d -p 8080:80 --name my-nginx nginx:latest

# List running containers
docker ps

# See ALL containers (including stopped)
docker ps -a

# View container logs
docker logs my-nginx

# Follow logs in real time (like tail -f)
docker logs -f my-nginx

# Stop and remove
docker stop my-nginx
docker rm my-nginx

# Remove an image
docker rmi nginx:latest

🌍 Real-World Use Case

A Node.js API depends on Node 18, specific npm packages, and environment variables. Without Docker, different developers have different Node versions and the CI server has yet another — causing mysterious failures. With Docker, everyone runs docker run myapp:1.0 and gets identical behavior. The same image is promoted from dev → staging → production with zero changes.

🧪 Hands-on Exercises

1. Run docker run hello-world to verify Docker is installed and working.
2. Run nginx on port 8080: docker run -d -p 8080:80 nginx, then visit http://localhost:8080.
3. Open a shell inside a running container: docker exec -it <container_id> /bin/sh
4. Pull alpine:latest and inspect its layers: docker image inspect alpine
5. Watch live resource usage: docker stats

🐛 Debugging Scenario

Problem: docker run myapp exits immediately and you see nothing.

# Step 1: check exit code
docker ps -a                     # see exit code column

# Step 2: read the logs
docker logs <container_id>      # check stdout/stderr

# Step 3: override CMD to get a shell
docker run -it myapp /bin/sh    # debug manually inside

# Common causes:
# - App crashes on startup (check logs for stack trace)
# - CMD/ENTRYPOINT wrong (no long-running process)
# - Missing env var (app exits with config error)

🎯 Interview Questions

📋 Summary

• Docker packages apps + dependencies into portable containers that run identically anywhere.
• Containers share the host kernel — much lighter and faster than VMs.
• Core objects: Image (template), Container (running instance), Dockerfile (build script), Registry (image store).
• Essential commands: docker run, docker ps, docker logs, docker stop.