Docker Practical Guide for Developers and DevOps Teams (Bernd Öggl, Michael Kofler)（Z-Library）

【One-Line Pitch】 A hands-on guide that takes developers and DevOps practitioners from installing Docker to building custom images, orchestrating multi-container apps, and handling security and operations. Best for readers who learn by doing and want a curated, exercise-driven path rather than scattered online tutorials. 【Book Arc】 - **Opening (~0%–10%)**: Frames the book's philosophy—curated, vetted content over fragmented web learning—and previews installation across Windows, macOS, Linux, Raspberry Pi, RHEL/Fedora, plus rootless Docker setup and troubleshooting. - **Early (~10%–23%)**: Establishes core terminology (images vs. containers, volumes, services/stacks/clusters, daemon vs. CLI) and gets you running containers interactively, with port redirecting, private networks, and multi-container communication (MariaDB, phpMyAdmin, WordPress). - **Early (~23%–32%)**: Moves into authoring custom images via Dockerfiles (FROM, ADD/COPY, CMD/ENTRYPOINT, RUN, VOLUME), pushing to Docker Hub, and orchestrating with Docker Compose and stack deploys, including secrets handling. - **Middle (~32%–48%)**: Covers practical tooling and internal details—VS Code Docker extension, Remote Containers, Portainer, Docker Hub pull limits, cross-architecture (ARM) work, auto-starting containers, and platform-specific backends (WSL2, macOS virtualization). - **Middle (~48%–60%)**: Serves as a command reference, cataloging `docker` and `docker-compose` subcommands (attach, build, exec, run, stats, swarm, system, volume, etc.) for lookup during daily work. - **Late/Ending (beyond ~60%)**: Excerpts do not cover the remaining chapters in detail; the blurb indicates later material addresses packaging new applications, modernizing existing ones, security, and operations exercises. 【Key Takeaways】 - **Containers are not VMs** (Early): The book draws the distinction explicitly, grounding mental models before you touch commands—essential for avoiding misapplied intuition. - **Images and containers are distinct but linked** (Early): Understanding this pairing, plus volumes and the daemon/CLI split, is the foundation everything else builds on. - **Communication between containers is a first-class skill** (Early): Private Docker networks, port redirecting, and a worked MariaDB/phpMyAdmin/WordPress stack show how real multi-service apps connect. - **Dockerfiles are the path to custom images** (Early): FROM, ADD vs. COPY, CMD vs. ENTRYPOINT, RUN, and VOLUME are covered with an introductory example and a custom web server image. - **Compose turns single containers into manageable stacks** (Early): The `docker-compose.yml` file, networks, named volumes, environment variables, restart behavior, and deploy settings are all addressed. - **Secrets deserve explicit handling** (Early): The book covers sharing database passwords between containers and secure secret exchange—not just "put it in an env var." - **Tooling and platform details matter in practice** (Middle): VS Code integration, Portainer, Docker Hub pull limits, ARM architecture, and WSL2/macOS backends are the friction points that trip up real teams. - **A command reference is part of the workflow** (Middle): The dedicated chapter on `docker` and `docker-compose` subcommands signals that the book expects you to return to it as a lookup, not just read once. 【Reading Tips】 - **Deep-read the Early sections on images, containers, and Dockerfiles**—these are the conceptual load-bearing walls; skimming them will make later chapters feel like memorization. - **Skim the installation chapter if your platform is already set up**, but bookmark the rootless Docker and troubleshooting subsections for when permissions or logging issues arise. - **Treat the command reference (Middle) as a lookup, not a read-through**—use it when a specific subcommand's flags or behavior are unclear. - **Work the exercises alongside the text**, especially the multi-container WordPress/MariaDB stack and the custom web server image; the book's value is in doing, not just reading. - **Pay attention to the secrets and security material** even if your current project is a toy—retrofitting secure secret handling later is more painful than learning it now. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book (installation through command reference); later chapters on packaging, modernizing, security, and operations exercises are only hinted at in the blurb and are not detailed here.