Book Image

The Docker Workshop

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

The Docker Workshop

5 (1)
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

Running Docker Containers

Best practices for building containers and microservices architecture dictate that a container should only run a single process. Keeping this principle in mind, we can design containers that are easy to build, troubleshoot, scale, and deploy.

The life cycle of a container is defined by the state of the container and the running processes within it. A container can be in a running or stopped state based on actions taken by the operator, the container orchestrator, or the state of the application running inside the container itself. For example, an operator can manually stop or start a container using the docker stop or docker start command-line interface (CLI) interface commands. Docker itself may automatically stop or restart a container if it detects that the container has entered an unhealthy state. Furthermore, if the primary application running inside the container fails or stops, the running container instance should also stop. Many container runtime...