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

Converting containers into images

We have learned about three different methods for building images, and all of them use containers in some shape or form. Let's review the container actions that can be used to create images:

commit

docker commit will allow us to create an image from a container. We will add a container's layer as a new image layer. As a result, we obtain a new image. We will set a new image name (although we learned that we can change image names whenever we need to) with its tag. The container will be paused during the commit to avoid file changes during its execution.

export

This action will create a .tar file containing the container's filesystem (including data from all of its layers). By default, this command will stream binary content to STDOUT, but we can use --output or -o to define a file for this content.

When we need to know about the changes we made to the original image layers, we can use docker container diff. This will show...