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

Service Dependency

Docker Compose runs and manages multi-container applications defined in docker-compose.yaml files. Although the containers are designed as independent microservices, creating services that depend on each other is highly expected. For instance, let's assume you have a two-tier application with database and backend components, such as a PostgreSQL database and a Java backend. The Java backend component requires PostgreSQL to be up and running since it should connect to the database to run the business logic. Therefore, you could need to define the dependency between the services of the multi-container applications. With Docker Compose, it is possible to control the order of the startup and shutdown of the services.

Say you have a three-container application with the following docker-compose.yaml file:

version: "3"
services:
  init:
    image: busybox
  pre:
    image: busybox
 &...