Master Docker from Zero to Pro: The Ultimate Beginner’s Guide

Docker Overview and History

Docker is a lightweight, portable container platform that emerged in 2010 from the company dotCloud and became open source in 2013. It quickly gained popularity due to its ability to package applications and their dependencies into isolated containers, offering faster deployment than traditional virtual machines.

Why Docker Is Faster Than VMs

Unlike VMs, Docker containers share the host kernel, eliminating the need to boot a full operating system for each instance. This reduces resource consumption and startup time from minutes to seconds.

Installing Docker

First, verify the kernel version (>=4.18) and OS version. Then remove any old Docker packages, add the official repository, and install docker-ce, docker-ce-cli, and containerd.io. Start the service and confirm the installation with docker version and docker info.

# Check kernel version
uname -r
# Check OS version
cat /etc/os-release
# Remove old versions
yum remove docker docker-client docker-common docker-engine
# Install prerequisites
yum install -y yum-utils
# Add repository
yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
# Install Docker
yum install -y docker-ce docker-ce-cli containerd.io
# Start Docker
systemctl start docker
# Verify
docker version

Basic Docker Commands

docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

– Create and start a container. docker ps – List running containers; add -a to show all. docker stop CONTAINER_ID – Stop a running container. docker rm CONTAINER_ID – Remove a stopped container. docker images – List local images. docker rmi IMAGE_ID – Delete an image. docker exec -it CONTAINER_ID /bin/bash – Open an interactive shell inside a container.

Working with Images

Docker images are built in layers using a UnionFS file system. Each command in a Dockerfile creates a new read‑only layer, while a container adds a writable top layer. This layered approach enables efficient storage and sharing of common base layers.

Creating Images with Dockerfile

A Dockerfile defines the steps to build an image. Example:

FROM centos:7
MAINTAINER YourName <[email protected]>
ENV APP_HOME /usr/local/app
WORKDIR $APP_HOME
RUN yum -y install vim net-tools
COPY . $APP_HOME
EXPOSE 80
CMD ["/bin/bash"]

Build the image with docker build -t mycentos:0.1 . and run it using docker run -d --name mycontainer mycentos:0.1.

Managing Data with Volumes

Docker volumes provide persistent storage that survives container removal. Use the -v flag to bind a host directory or a named volume to a container path.

# Bind a host directory
docker run -d -v /host/data:/container/data myimage
# Create and use a named volume
docker volume create mydata
docker run -d -v mydata:/var/lib/mysql mysql:5.7

Volumes can be shared among multiple containers, enabling data persistence and inter‑container data sharing.

Docker Networking

By default, containers attach to the bridge network (docker0), receiving an IP in the 172.17.0.0/16 range. Containers on the same bridge can ping each other, but they cannot resolve each other by name.

For name resolution and isolation, create a user‑defined bridge network:

# Create a custom network
docker network create --driver bridge --subnet 192.168.0.0/16 mynet
# Run containers on the custom network
docker run -d --name app1 --net mynet nginx
docker run -d --name app2 --net mynet nginx
# Containers can now ping each other by name
docker exec app1 ping app2

Custom networks also allow you to connect containers from different networks using docker network connect.

Advanced Topics

Using docker commit to snapshot a container’s state as a new image.

Building multi‑stage images to reduce final image size.

Running containers with --restart=always for high availability.

This guide provides the essential knowledge to install Docker, manage containers, create images, handle persistent storage, and configure networking, enabling you to adopt containerization in development and production environments.