As we have seen, it's really easy to spin up and shut down the Docker containers. Wouldn't it be useful if we could do that as a part of a build?
In a perfect world, our build process would build our application and then install it in a Docker container. We would then be able to run tests against this container, and if everything worked as expected, we could publish the container in a private Docker registry. We could then take this Docker container and pass it through our promotional model until it hits live. We would then have something in live that is identical to the container that we originally built and tested. Thus, we would know that it works. If we have any problems with it in live, we can easily spin up another instance of this container in a test environment to reproduce the problem. Rather than passing around application installers, we can instead pass around preinstalled and working applications.
Let's have a look at how we can...