Docker Demystified Learn How to Develop and Deploy Applications Using Docker (Saibal Ghosh)（Z-Library）

【One-Line Pitch】 A practical, hands-on guide to Docker that takes you from "why containers exist" to building, networking, and orchestrating real applications. Best for developers and ops engineers who want working commands and mental models, not just theory. 【Book Arc】 - **Opening (~0%–10%)**: Frames the problem — monolithic apps, environment mismatches — and introduces containers, microservices, and Docker's client-server architecture as the answer. - **Early (~10%–30%)**: Gets hands-on with the Docker Engine internals (dockerd, containerd, runC), images and layers, and the Dockerfile build workflow. - **Early–Middle (~30%–40%)**: Explores storage — the read-write layer, storage drivers (overlay2), and data persistence via volumes, bind mounts, and tmpfs. - **Middle (~40%–50%)**: Builds networking from the ground up: network namespaces, Linux bridges, veth pairs, libnetwork, and the docker0 bridge. - **Middle–Late (~50%+)**: Moves to orchestration with Docker Swarm — clustering, service discovery, overlay networks, rolling updates, and built-in TLS security. - **Late (excerpts do not cover)**: A dedicated security chapter is referenced but its detailed content is not present in the excerpts. 【Key Takeaways】 - **Containers solve the "works on my machine" problem** (Opening): by packaging code with its dependencies into a portable, consistent unit that shares the host OS kernel. - **Docker's architecture is layered** (Early): the CLI talks to the daemon (dockerd), which delegates to containerd, which relies on runC — understanding this stack clarifies where things go wrong. - **Images are read-only, layered templates** (Early): each Dockerfile line creates a layer, enabling caching and efficient rebuilds; multi-stage builds help control image size. - **Data persistence requires deliberate design** (Middle): the container's writable layer is ephemeral, so volumes and bind mounts are essential for production, with performance trade-offs to weigh. - **Networking rests on Linux primitives** (Middle): network namespaces provide isolation, veth pairs connect containers, and the docker0 bridge is the foundation — not magic, just Linux. - **Swarm offers built-in orchestration** (Late): service discovery, load balancing, rolling updates, and TLS mutual authentication come natively, with minimal setup. - **Log management is a real operational concern** (Early): container and host logs multiply quickly, so a centralized aggregator plus log rotation is a best practice, not an afterthought. 【Reading Tips】 - **Deep-read the Dockerfile and storage chapters** — these are the highest-leverage for daily work; skim the conceptual opening if you already know why containers matter. - **Run every command as you read.** This is a lab-driven book; the value is in typing `docker run`, `docker build`, and `docker inspect` yourself. - **Don't skip the networking chapter even if it feels low-level.** The namespace/veth/bridge model pays off when debugging connectivity issues later. - **Treat the review questions and key terms as checkpoints** — they signal what the author considers essential. - **Note the security chapter's absence in these excerpts** and seek it out separately if security is your priority. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book (through Swarm orchestration); the dedicated security chapter and any later advanced topics are referenced but not detailed here.