What is Docker? Complete Beginner Guide with Examples

What is Docker?#

Docker is a container platform that helps developers package an application with its dependencies and run it consistently across laptops, servers, CI/CD systems, and cloud environments.

Animated explanation: Docker in one flow#

Quick answer#

Docker image#

A read-only package that contains application code, runtime, libraries, and dependencies.

Docker container#

A running instance of an image. It is isolated but shares the host operating system kernel.

Dockerfile#

A text file containing instructions to build a Docker image.

Why Docker is useful#

Without Docker, applications often work on one machine but fail on another because of different versions, missing libraries, different operating system packages, or environment configuration. Docker reduces this issue by packaging the application and its runtime requirements together.

Simple real-world example#

Imagine a Node.js application that needs Node 20, npm packages, environment variables, and port 3000. Instead of installing everything manually on every server, you build one image and run it anywhere Docker is available.

docker run hello-world

The above command downloads a test image and runs a container. It is the simplest way to verify Docker works.

Docker vs Virtual Machine#

• Area — Docker Container — Virtual Machine
• Startup — Usually fast — Usually slower
• Size — Smaller — Larger
• Isolation — Process-level — Full OS-level
• Use case — Apps and services — Full OS environments

Basic Docker workflow#

1. Write application code.
2. Create a Dockerfile.
3. Build an image using docker build .
4. Run a container using docker run .
5. Push the image to a registry if it should be shared.
6. Deploy the image using Docker, Compose, Kubernetes, or CI/CD.

Important commands#

docker --version docker pull nginx docker run -d -p 8080:80 nginx docker ps docker logs CONTAINER_ID docker stop CONTAINER_ID

Common mistakes#

• Thinking a container is a full virtual machine.
• Putting secrets inside Docker images.
• Using only the latest tag for production images.
• Not understanding volumes before running databases.
• Opening container ports without checking security.

Best practices#

• Use small official base images where possible.
• Keep Dockerfiles readable.
• Use environment variables for runtime configuration.
• Use volumes for persistent data.
• Use custom networks for multi-container apps.
• Use CI/CD to build and scan images.

Related Melochip guides#

• Docker Learning Path
• GitLab CI/CD Docker Build Pipeline
• Kubernetes Cluster Setup Guide

Official references#

• Docker Get Started documentation
• Docker Engine documentation