Docker Cookbook (Sébastien Goasguen)（Z-Library）

【One-Line Pitch】 A practical, recipe-driven guide for developers, operators, and IT professionals who want to move from Docker basics to building, sharing, and orchestrating containerized applications—including hands-on coverage of Kubernetes, Swarm, and other ecosystem tools. 【Book Arc】 - **Opening (~0%–9%)**: Sets expectations for an intermediate audience, listing prerequisites (Bash, package management, Git, Python, Vagrant) and outlining the cookbook structure—from first steps to production deployment. - **Early (~9%–25%)**: Covers Docker fundamentals: running your first container (`hello world`), managing images and containers, using data containers for volume sharing, and linking containers (e.g., WordPress + MySQL). Introduces the idea of single-purpose containers. - **Early (~25%–34%)**: Moves to image creation and sharing: writing your first Dockerfile (FROM, ENTRYPOINT), tagging images for versioning, and using Packer to build images from existing provisioning workflows (shell, Ansible, Chef). - **Middle (~34%–47%)**: Explores networking options in depth: default bridge, `--net=none`, `--net=host` (with warnings about security), and sharing another container's network stack. Emphasizes isolation and the risks of privileged containers. - **Middle (~47%–end)**: Expands into the Docker ecosystem: Docker Compose for multi-container apps (WordPress, Mesos/Marathon), Swarm for clustering, Docker Machine for cloud provisioning, and orchestration tools like Kubernetes, Rancher, and Mesos—plus service discovery with Registrator. 【Key Takeaways】 - **Start with the lifecycle of a container** (Early): Learn `docker run`, `docker ps -a`, `docker rm`, and `docker rmi` to understand that containers exit after their task, but images persist locally. This foundation prevents confusion later. - **Use data containers for shared, persistent volumes** (Early): By omitting the host path in `-v`, Docker manages the volume; use `--volumes-from` to share it across containers. This keeps storage decoupled from any single container's lifecycle. - **Link containers for simple service discovery** (Early): The `--link` flag lets a WordPress container talk to a MySQL container without exposing ports publicly—a quick way to build multi-container apps before moving to orchestration. - **Automate image builds with Dockerfiles** (Early): A Dockerfile (FROM, ENTRYPOINT, CMD, EXPOSE) turns manual container commits into repeatable, shareable build steps. This is the core of reproducible infrastructure. - **Tag images for versioning and sharing** (Early): Use `docker tag` to assign meaningful repository names (e.g., `how2dock/flask`) before pushing to Docker Hub; layers already present are skipped, making pushes efficient. - **Choose networking stacks deliberately** (Middle): `--net=none` gives isolation, `--net=host` shares the host's interfaces (dangerous with `--privileged`), and sharing another container's stack enables specific topologies. Understand the trade-offs before choosing. - **Orchestration is the next step after single-host Docker** (Middle): Tools like Compose, Swarm, and Kubernetes solve multi-container, multi-host problems—but they build on the same image and container primitives you've already mastered. 【Reading Tips】 - **Skim the first chapters if you're not a beginner**: The early recipes (hello world, data containers, linking) are foundational but simple; focus on the Dockerfile and networking sections for deeper insights. - **Deep-read the networking chapter (Chapter 3)**: It's the most technical and security-sensitive part—pay attention to the warnings about `--net=host` and privileged containers. - **Use the ecosystem chapter as a reference, not a tutorial**: Recipes for Compose, Swarm, Kubernetes, and Mesos are broad; pick one tool that matches your deployment target and follow that recipe end-to-end. - **Try the Packer recipe if you're migrating from VMs**: It bridges traditional provisioning (Ansible, Chef) with Docker, which is valuable for teams with existing DevOps workflows. - **Keep a terminal handy**: The book is full of command-line examples; running them as you read will cement the concepts faster than reading alone. 【Coverage Limits】 This guide synthesizes the provided excerpts, which cover roughly the first half of the book (fundamentals, image creation, networking) and a table of contents for the ecosystem chapters. Detailed recipes for Kubernetes, Swarm, and production monitoring are not fully covered in the source material.