Docker Explained: Containers for Developers

Containers vs Virtual Machines

Virtual machines emulate full hardware stacks — heavy but isolated. Containers share the host OS kernel but package application code, runtime, and dependencies into portable images. They start in seconds and use less memory, which is why modern deployment pipelines default to containers.

Think of an image as a recipe and a container as a running instance of that recipe. Dockerfile instructions layer on top of each other, cached for fast rebuilds.

Docker Workflow for Developers

Docker Compose is invaluable for local full stacks: web app + database + Redis without manual install scripts on every machine.

• docker build -t myapp . — create image from Dockerfile.
• docker run -p 3000:3000 myapp — start container with port mapping.
• docker ps / docker logs — inspect running containers.
• docker compose up — orchestrate multi-service stacks locally.

Production Considerations

Do not run containers as root in production. Scan images for vulnerabilities. Use multi-stage builds to keep final images small — drop build tools from what ships.

Kubernetes orchestrates containers at scale, but understand Docker fundamentals first. Most K8s pain comes from not knowing what the container image actually contains.