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

Docker tags for security

We've just seen how we can make sure we are sharing secrets securely between containers in a swarm. In Chapter 12, Introduction to Container Security, we gained an appreciation for how to use tags combined with other security features, to ensure we use the correct image.

Now, we'll see how these two worlds can intersect by using tags with secrets and labels so we can annotate which environment a given secret and tag are used in.

As a good security practice, we should always use different secrets for different environments. For example, the passwords for database access in your development, staging, and production instances should not be the same. Typically, as part of your development process, you will likely be using newer versions of containers in research, development, and QA environments compared to production.

We can use Docker tags to help ensure that once we have credentials/secrets set up for a development environment, we are also...