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

Attaching to Containers Using the attach Command

In the previous exercise, you saw how to use the docker exec command to spin up a new shell session in a running container instance in which to execute commands. The docker exec command is very good for quickly gaining access to a containerized instance for debugging, troubleshooting, and understanding the context the container is running in.

However, as covered earlier in the chapter, Docker containers run as per the life of the primary process running inside the container. When this process exits, the container will stop. If you wanted to access the primary process inside the container directly (as opposed to a secondary shell session), then Docker provides the docker attach command to attach to the primary running process inside the container.

When using docker attach, you are gaining access to the primary process running in the container. If this process is interactive, such as a Bash or Bourne shell session, you will be...