Docker Basics for Developers — Containers, Images, and Compose Explained

What Is Docker?

Docker is a platform for building, shipping, and running applications in containers. A container packages your application code with all its dependencies — runtime, libraries, configuration — into a single, portable unit. Unlike virtual machines, containers share the host OS kernel, making them lightweight and fast to start.

Docker solves the classic "works on my machine" problem. If it runs in a container on your laptop, it runs the same way in CI/CD, staging, and production. For developers, Docker is primarily a tool for consistent environments; for operations teams, it's a foundation for scalable deployments.

How to Get Started with Docker Basics

1. Install Docker Desktop for Mac or Windows, or Docker Engine for Linux from docker.com.
2. Run your first container: docker run hello-world to verify installation.
3. Pull an image: docker pull node:20-alpine downloads the Node.js Alpine image.
4. Write a Dockerfile to define how your app image is built.
5. Build and run your image: docker build -t myapp . && docker run -p 3000:3000 myapp
6. Use Docker Compose for multi-container applications (app + database + cache).

Key Concepts

• Image — A read-only template for creating containers. Built from a Dockerfile. Stored in registries like Docker Hub or GitHub Container Registry.
• Container — A running instance of an image. Isolated process with its own filesystem, network, and process space.
• Dockerfile — A text file with instructions (FROM, RUN, COPY, CMD) that define how an image is built.
• Docker Compose — A YAML file (compose.yml) that defines multiple services, networks, and volumes for a multi-container application.
• Volume — Persistent storage that survives container restarts. Used for databases and file uploads.
• Registry — A repository for Docker images. Docker Hub is the public default; private registries include ECR, GCR, and GitHub Packages.

Use Cases

Local Development Environments

Docker Compose lets you spin up a full stack — Node.js app, PostgreSQL, Redis — with a single docker compose up command. New team members get a working environment in minutes, not hours. No more "install PostgreSQL version X" onboarding docs.

CI/CD Pipelines

Docker containers are the standard unit of CI/CD in 2026. GitHub Actions, GitLab CI, and CircleCI all run jobs inside containers, ensuring reproducible build and test environments. Your app is built into an image, tested, and pushed to a registry in a single pipeline.

Microservices Architecture

Each microservice runs in its own container, enabling independent deployment, scaling, and versioning. Container orchestration platforms like Kubernetes manage container clusters at scale, but Docker is the foundation for each individual service.

Frequently Asked Questions

What is the difference between a Docker container and a virtual machine?

Virtual machines emulate entire hardware and run a full OS. Containers share the host OS kernel and isolate only the application and its dependencies. Containers start in milliseconds, use significantly less memory, and are more portable. VMs provide stronger isolation when required by security policies.

What should go in a .dockerignore file?

The .dockerignore file works like .gitignore — it prevents files from being sent to the Docker build context. Always exclude node_modules, .git, .env files, and build artifacts to keep images lean and secure.

How do I make my Docker images smaller?

Use Alpine-based images (node:20-alpine instead of node:20), use multi-stage builds to separate build dependencies from runtime, minimize the number of layers, and clean up package manager caches in the same RUN command that installs packages.

What is Docker Compose used for?

Docker Compose defines and runs multi-container applications. A compose.yml file describes your services, their images or build contexts, port mappings, environment variables, and dependencies. Run the entire stack with docker compose up -d.

Should I use Docker in production?

Yes, Docker containers are the standard deployment artifact for containerized production workloads. For managed deployments, services like AWS ECS, Google Cloud Run, and Fly.io run Docker containers directly. For self-managed clusters, Kubernetes orchestrates containers at scale.