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

Interacting with containers

We can interact with running or stopped containers. We need to interact with containers to run some processes within them, review some of their files, or retrieve the main process output. These are the main actions we will use to interact with containers:

attach

Using attach, we will be able to connect to the main process's STDIN/STDOUT/STDERR. In other terms, we will be attached to this process to interact with it. Be careful because sending a signal with your keyboard may interrupt the process and container's life (we can omit this behavior using --sig-proxy false). We can only attach to running containers.

cp

This action will allow us to send /receive content to/from the container's filesystem. It acts as a normal copy but we can maintain file ownership using --archive. We will just use the source path and destination and we will use the <container>:</path_to_file> notation to reference files inside containers. Containers...