If you run docker compose up repeatedly from the same Compose file, no changes will be made after the first run. Docker Compose compares the configuration in the Compose file with the active containers at runtime and won't change resources unless the definition has changed. This means you can use Docker Compose to manage application upgrades.
My Compose file is currently using the database service from the image I built in Chapter 3, Developing Dockerized .NET Framework and .NET Core Applications, tagged dockeronwindows/ch03-nerd-dinner-db:2e. For this chapter, I've added audit fields to the tables in the database schema and built a new version of the database image, tagged dockeronwindows/ch06-nerd-dinner-db:2e ...
