Book Image

A Developer's Essential Guide to Docker Compose

By : Emmanouil Gkatziouras
Book Image

A Developer's Essential Guide to Docker Compose

By: Emmanouil Gkatziouras

Overview of this book

Software development is becoming increasingly complex due to the various software components used. Applications need to be packaged with software components to facilitate their operations, making it complicated to run them. With Docker Compose, a single command can set up your application and the needed dependencies. This book starts with an overview of Docker Compose and its usage and then shows how to create an application. You will also get to grips with the fundamentals of Docker volumes and network, along with Compose commands, their purpose, and use cases. Next, you will set up databases for daily usage using Compose and, leveraging Docker networking, you will establish communication between microservices. You will also run entire stacks locally on Compose, simulate production environments, and enhance CI/CD jobs using Docker Compose. Later chapters will show you how to benefit from Docker Compose for production deployments, provision infrastructure on public clouds such as AWS and Azure, and wrap up with Compose deployments on said infrastructure. By the end of this book, you will have learned how to effectively utilize Docker Compose for day-to-day development.
Table of Contents (19 chapters)
1
Part 1: Docker Compose 101
6
Part 2: Daily Development with Docker Compose
12
Part 3: Deployment with Docker Compose

Container commands

Container commands enable us to start, stop, and restart containers, execute commands upon them, and also kill them.

exec

Throughout the book, we have executed commands using the Docker exec command. Docker Compose also provides this functionality. The difference is that instead of running the exec command directly to a container on Compose, we specify the service to execute upon. The command then will be routed to the service’s underlying container:

$ docker compose exec task-manager ls
go.mod    go.sum    main.go         

If we check the existing containers, we will not see any extra containers provisioned:

$ docker ps -a                       
CONTAINER ID   IMAGE             &...