Docker lets you package an application with everything it needs to run, so it works the same on your laptop, your server, and your colleague's machine. That promise, it works on my machine becomes it works everywhere, is why Docker became the standard for modern development. This guide takes you from zero to a running container in one afternoon.

What Docker Actually Does

Docker packages your application and its dependencies into a container, a lightweight, isolated environment that runs the same everywhere. Unlike a virtual machine, a container shares the host's operating system kernel, so it starts in seconds and uses far less memory. The image is the blueprint, the container is the running instance, and the Dockerfile is the recipe that builds the image. Once you understand those three ideas, Docker makes sense.

Your First Dockerfile

A Dockerfile is a short text file that describes how to build your image: start from a base image, copy your code, install dependencies, expose a port, and set the command to run. A simple Node.js app needs about ten lines, and a Python app needs about the same. Build the image with one command, run it with another, and your app is live in a container. Keep images small by using slim base images and removing build tools after installation.

Running and Managing Containers

The docker run command starts a container, docker ps lists running containers, and docker stop and docker rm clean them up. Map ports so the container's internal port is reachable from your machine, and mount volumes so data survives when the container stops. Use docker logs to see what your app is doing, and docker exec to run a command inside a running container. These five commands cover 90% of daily Docker use.

Docker Compose for Multi-Container Apps

Most real apps need more than one container: a web app plus a database, or an app plus a cache. Docker Compose defines all of them in one YAML file and starts them together with a single command. It handles networking between containers, volumes for data, and environment variables for configuration. Learn Compose as soon as you have a working single container, because it is how real projects are run.

Docker Security Basics

Never run containers as root unless you must, and never expose the Docker socket to a container. Keep base images updated, scan images for known vulnerabilities, and do not bake secrets into images: pass them as environment variables or use a secrets manager. A container is not a security boundary by itself, so treat it as one layer among several. These basics take an hour to learn and prevent the most common Docker mistakes.

Docker in the Real World

Docker's real value appears when you deploy: the same container that runs on your laptop runs on the server, which eliminates the works on my machine problem that plagues every team. Learn the deployment side early, not just the local side: push your image to a registry, pull it on a server, and run it with a restart policy. The skills are the same, but the context is different, and the deployment is where Docker earns its reputation. A container you never deploy is a lesson half-learned.

Key Takeaways

- A container packages your app and its dependencies so it runs anywhere - A Dockerfile is a short recipe: base image, copy code, install, expose, run - Five commands cover 90% of Docker use: run, ps, stop, rm, logs - Docker Compose runs multi-container apps from one file

Frequently Asked Questions

How do I start with Docker? Install Docker, write a ten-line Dockerfile for a simple app, build the image, and run it. Then learn Docker Compose for multi-container apps.

Docker turns it works on my machine into it works everywhere. Build your first container today, then learn Compose.