Book Image

The Docker Workshop

By : Vincent Sesto, Onur Yılmaz, Sathsara Sarathchandra, Aric Renzo, Engy Fouda
5 (3)
Book Image

The Docker Workshop

5 (3)
By: Vincent Sesto, Onur Yılmaz, Sathsara Sarathchandra, Aric Renzo, Engy Fouda

Overview of this book

No doubt Docker Containers are the future of highly-scalable software systems and have cost and runtime efficient supporting infrastructure. But learning it might look complex as it comes with many technicalities. This is where The Docker Workshop will help you. Through this workshop, you’ll quickly learn how to work with containers and Docker with the help of practical activities.? The workshop starts with Docker containers, enabling you to understand how it works. You’ll run third party Docker images and also create your own images using Dockerfiles and multi-stage Dockerfiles. Next, you’ll create environments for Docker images, and expedite your deployment and testing process with Continuous Integration. Moving ahead, you’ll tap into interesting topics and learn how to implement production-ready environments using Docker Swarm. You’ll also apply best practices to secure Docker images and to ensure that production environments are running at maximum capacity. Towards the end, you’ll gather skills to successfully move Docker from development to testing, and then into production. While doing so, you’ll learn how to troubleshoot issues, clear up resource bottlenecks and optimize the performance of services. By the end of this workshop, you’ll be able to utilize Docker containers in real-world use cases.
Table of Contents (17 chapters)
Preface

Docker Volumes and Stateful Persistence

We can use volumes to save persistent data without relying on the containers. You can think of a volume as a shared folder. In any instance, if you mount the volume to any number of containers, the containers will be able to access the data in the volume. There are two ways to create a volume:

  • Create a volume as an independent entity outside any container by using the docker volume create subcommand.

    Creating a volume as an independent object from the container adds flexibility to data management. These types of volumes are also called named volumes because you specify a name for it, rather than leaving the Docker Engine to generate an anonymous numeric one. Named volumes outlive all the containers that are in the system and preserve its data.

    Despite these volumes being mounted to containers, the volumes will not be deleted even when all the containers in the system are deleted.

  • Create a volume by using the --mount or -v or --volume...