Book Image

Docker for Developers

By : Richard Bullington-McGuire, Andrew K. Dennis, Michael Schwartz
2 (1)
Book Image

Docker for Developers

2 (1)
By: Richard Bullington-McGuire, Andrew K. Dennis, Michael Schwartz

Overview of this book

Docker is the de facto standard for containerizing apps, and with an increasing number of software projects migrating to containers, it is crucial for engineers and DevOps teams to understand how to build, deploy, and secure Docker environments effectively. Docker for Developers will help you understand Docker containers from scratch while taking you through best practices and showing you how to address security concerns. Starting with an introduction to Docker, you’ll learn how to use containers and VirtualBox for development. You’ll explore how containers work and develop projects within them after you’ve explored different ways to deploy and run containers. The book will also show you how to use Docker containers in production in both single-host set-ups and in clusters and deploy them using Jenkins, Kubernetes, and Spinnaker. As you advance, you’ll get to grips with monitoring, securing, and scaling Docker using tools such as Prometheus and Grafana. Later, you’ll be able to deploy Docker containers to a variety of environments, including the cloud-native Amazon Elastic Kubernetes Service (Amazon EKS), before finally delving into Docker security concepts and best practices. By the end of the Docker book, you’ll be able to not only work in a container-driven environment confidently but also use Docker for both new and existing projects.
Table of Contents (21 chapters)
1
Section 1: An Introduction to Docker – Containers and Local Development
6
Section 2: Running Docker in Production
14
Section 3: Docker Security – Securing Your Containers

Chapter 7: Continuous Deployment with Jenkins

In order to reliably use Docker containers in production, you need a process that will consistently build, test, and deploy your software. A team building very small applications might be satisfied with running tests and deployment scripts manually. However, discipline often breaks down, and people step on each other's toes. This often results in broken builds and tests that are not run before or after a production deployment. The aftermath is often downtime and unhappy customers. In order to make sure that we can build, test, and deploy software reliably, we can use continuous integration software. This type of software can reliably build, test, and deploy revisions in a disciplined and traceable way. A well-run modern project can even use this software to achieve continuous deployment, where even the smallest changes to the software can be quickly promoted to either a test or production environment.

In this chapter, we show how...