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

Summary

This chapter was dedicated to the Docker command line and running containers. We found a powerful command line that allowed us to create containers from image artifacts, share them between hosts, and execute the already built application components.

We learned how to interact with different Docker objects, as well as what kind of objects are available in standalone Docker host environments and what objects are available in orchestrated environments.

We then reviewed how containers can be created, executed, paused/unpaused, and stopped or killed. They will stay in our Docker host until they are removed from the system. We also learned how to manipulate the container's execution behavior and how they exist within the network. To improve security, we introduced a number of options and we also learned how executing containers in read-only mode can be very useful.

Limiting the container's resources is necessary for production. By default, they will be able to consume all...