Simplify All the Things with Docker Compose


    As you probably know by now, containers have revolutionized the software industry. But, once you have a container, then what? How do you run it? How do you help someone else run it? There are so many flags and options to remember, ports to configure, volume mappings to remember, and don’t even get me started with networking containers together! While it’s possible to do all of this through the command line, don’t do it that way! With Docker Compose, you can create an easily shareable file that makes all of this a piece of cake. And once you fully adopt containers in your dev environment, it lets you setup your code repos to allow the simplest dev onboarding experience imaginable: 1) git clone; 2) docker-compose up; 3) write code.

    In this talk, we’ll talk about several tips to help make all of this a reality. We’ll start with a few Docker Compose basics, but then quickly move into several advanced topics. We’ll even talk about how to use the same Dockerfile for dev and prod (we’ve all been there by having two separate files)! As an added bonus, we’ll look at how to use Docker Compose in our CI/CD pipelines to perform automated tests of the container images built earlier in the pipeline!

    We’ll have a few slides (because we have to explain a few things), lots of live demos (show it in action!), and maybe a few other surprises as well! Let’s have some fun and help simplify all the things with Docker Compose!

    Speaker: Michael Irwin, Virginia Tech
    Twitter: @mikesir87


    Previous articleGemlest – Azure (Official Audio)
    Next articleHow to create AKS Cluster | Setting Up & Deploying an Azure Kubernetes Service Cluster | K21Academy


    1. Great talk! I'm newer to docker and understand the concept of mapping a local directory to a directory in the image so you use your local files to do development… In your docker compose file you have the named volume "nodemodules" that's mapped to the /node_modules directory in the image. What is that doing within your dev environment if it's not linked to the /node_modules in your local directory?