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

Performing PromQL Queries

Running queries on the expression browser is easy, but you may not always get the information you need. By simply adding the metric name, such as countainer_cpu_system_seconds_total, we can get quite a few responses. Though, the amount depends on the number of containers we have on our system along with the returning values for each of the filesystems that are running on our host system. To limit the number of responses provided in our result, we can search for specific text using curly braces { }.

Consider the following examples. The following command provides the full name of the "cadvisor" container we wish to view:

container_cpu_system_seconds_total{ name="cadvisor"}

The following example uses a regular expression compatible with GO. The command looks for any names that start with ca and have further characters afterward:

container_cpu_system_seconds_total{ name=~"ca.+"} 

The following code snippet is searching...