You're reading from Docker for Developers Develop and run your application with Docker containers using DevOps tools for continuous delivery

Product type Paperback

Published in Sep 2020

Publisher Packt

ISBN-13 9781789536058

Length 468 pages

Edition 1st Edition

Tools

Docker

Concepts

Containerization

Authors (3):

Richard Bullington-McGuire

Michael Schwartz

Andrew K. Dennis

View More author details

Table of Contents (21) Chapters

Preface

1. Section 1: An Introduction to Docker – Containers and Local Development

2. Chapter 1: Introduction to Docker FREE CHAPTER

3. Chapter 2: Using VirtualBox and Docker Containers for Development

4. Chapter 3: Sharing Containers Using Docker Hub

5. Chapter 4: Composing Systems Using Containers

6. Section 2: Running Docker in Production

7. Chapter 5: Alternatives for Deploying and Running Containers in Production

8. Chapter 6: Deploying Applications with Docker Compose

9. Chapter 7: Continuous Deployment with Jenkins

10. Chapter 8: Deploying Docker Apps to Kubernetes

11. Chapter 9: Cloud-Native Continuous Deployment Using Spinnaker

12. Chapter 10: Monitoring Docker Using Prometheus, Grafana, and Jaeger

13. Chapter 11: Scaling and Load Testing Docker Applications

14. Section 3: Docker Security – Securing Your Containers

15. Chapter 12: Introduction to Container Security

16. Chapter 13: Docker Security Fundamentals and Best Practices

17. Chapter 14: Advanced Docker Security – Secrets, Secret Commands, Tagging, and Labels

18. Chapter 15: Scanning, Monitoring, and Using Third-Party Tools

19. Chapter 16: Conclusion – End of the Road, but not the Journey

20. Other Books You May Enjoy

Leave a review - let other readers know what you think

Binding a host filesystem within containers

Previously, we used a third docker-compose configuration file to specify bindings so that our source code directory would be overlaid within the container (in place of the app's home directory). We will do the same for the latest incarnation of our Docker Compose setup.

We first create a docker-compose-dev.yml file:

version: '3'
services:
  publisher:
    volumes:
      - ./publisher:/home/app
  subscriber:
    volumes:
      - ./subscriber:/home/app

This override file simply maps the publisher and subscriber source code directory over /home/app in the related container. Now, we can freely edit sources on the host and, thanks to nodemon, our changes will take effect almost immediately within the running containers. There is no need to stop, rebuild, or restart any containers.

Unfortunately, docker...