Skip to content

Docker Overview

What Docker is, how containers work, and why they revolutionized software deployment.

What you'll learn

  • What Docker is and the problem it solves
  • Containers vs virtual machines
  • The Docker architecture: engine, images, and containers
  • Core Docker commands

Concept

What Is Docker?

Docker is a platform for building, running, and managing applications in containers. A container is a lightweight, standalone package that includes your application code plus everything it needs to run — libraries, system tools, configuration — all isolated from the host system. Docker solves the "it works on my machine" problem by guaranteeing that an application runs identically wherever its container runs.

Containers vs Virtual Machines

A virtual machine (VM) runs a full operating system with its own kernel, which makes it heavy and slow to start. A container shares the host operating system's kernel and only isolates the application processes. This makes containers much smaller (megabytes vs gigabytes) and faster to start (seconds vs minutes). You can run dozens of containers on a single machine where you could only fit a few VMs.

Docker Architecture

Docker uses a client-server architecture. The Docker client (docker command) talks to the Docker daemon (server), which builds, runs, and manages containers. An image is a read-only template with instructions for creating a container — think of it as a blueprint. A container is a running instance of an image. Images are stored in registries like Docker Hub or a private registry.

Core Commands

The essential Docker commands are simple. docker build creates an image from a Dockerfile. docker run starts a container from an image. docker ps lists running containers. docker images lists available images. docker stop and docker rm stop and remove containers. These commands are the foundation of all Docker workflows.

The Docker Ecosystem

Docker is more than just a container runtime. Docker Hub is a public registry with millions of pre-built images. Docker Compose orchestrates multi-container applications. Docker Swarm provides native clustering. The broader ecosystem includes Kubernetes for large-scale orchestration, containerd as a lightweight runtime, and Podman as a daemonless alternative. Understanding Docker is the entry point to this entire ecosystem — the concepts of images, containers, and registries carry over to every tool that builds on Docker's foundation.

Example

              # Pull and run a ready-made image
docker pull nginx:alpine
docker run -d --name web -p 8080:80 nginx:alpine

# Inspect what is running
docker ps                        # list running containers
docker ps -a                     # list all containers (including stopped)
docker images                    # list available images
docker logs web                  # view container logs

# Stop and clean up
docker stop web
docker rm web
docker rmi nginx:alpine          # remove the image
            

docker pull downloads an image, docker run starts a container, docker ps lists containers, and docker logs shows output. These are the daily Docker commands.

Try it

Common mistakes

The mistake

Running containers as root by default

The fix

Create a non-root user in your Dockerfile and switch to it with USER. Running as root inside a container is a security risk if an attacker escapes the container.

The mistake

Not cleaning up stopped containers and images

The fix

Use docker system prune regularly to remove unused containers, images, and networks. They accumulate quickly and consume disk space.

Practice Docker Overview

1 exercise

Practice Docker Overview

Look up unfamiliar terms

A beginner-friendly glossary explains jargon in plain English — variables, functions, DOM, Promise, and more.

View glossary

Build real projects

Apply what you learned by building guided projects with starter code and solutions.

View projects

Decode error messages

Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.

View errors