Book Image

Docker Certified Associate (DCA): Exam Guide

By : Francisco Javier Ramírez Urea
Book Image

Docker Certified Associate (DCA): Exam Guide

By: Francisco Javier Ramírez Urea

Overview of this book

Developers have changed their deployment artifacts from application binaries to container images, and they now need to build container-based applications as containers are part of their new development workflow. This Docker book is designed to help you learn about the management and administrative tasks of the Containers as a Service (CaaS) platform. The book starts by getting you up and running with the key concepts of containers and microservices. You'll then cover different orchestration strategies and environments, along with exploring the Docker Enterprise platform. As you advance, the book will show you how to deploy secure, production-ready, container-based applications in Docker Enterprise environments. Later, you'll delve into each Docker Enterprise component and learn all about CaaS management. Throughout the book, you'll encounter important exam-specific topics, along with sample questions and detailed answers that will help you prepare effectively for the exam. By the end of this Docker containers book, you'll have learned how to efficiently deploy and manage container-based environments in production, and you will have the skills and knowledge you need to pass the DCA exam.
Table of Contents (22 chapters)
1
Section 1 - Key Container Concepts
8
Section 2 - Container Orchestration
12
Section 3 - Docker Enterprise
17
Section 4 - Preparing for the Docker Certified Associate Exam

Limiting host resources

We have seen some options for limiting the container's resource consumption. We will be able to limit access to CPU, memory, and block devices. There are two types of limits when we focus on memory resources: soft and hard limits.

Soft limits will represent a reservation of resources. This means that a container could consume more memory than declared, but this value will be reserved.

On the other hand, a hard limit will ensure that no more than the declared value will be consumed. In fact, the container will die if this limit is surpassed. An out-of-memory (also known as OOM) killer will kill the main process to prevent host problems.

Remember that, by default, if you do not specify any limits, containers will be able to consume all your host resources.

There are many options available to ensure limited access to resources. We can modify default cgroups settings automatically with these parameters:

--cpu-period

and

--cpu-quota

CFS is the Linux kernel...