

When you Enable Docker Support a Docker Compose project is created.

It has been possible to run ASP.NET/.NET Core on Linux, but I have been waiting to be able to do this on Windows. With Windows Server 2016 having Docker support, it’s time to get on board. There are other reasons, but they had me at “create new test environments without having to go through the tiring dance…” So, Docker delivers on “ infrastructure as code” and allows you to save your Docker container configuration in source control and iterate it along with the source code. So, each test deployment gets a brand new fresh environment and the environment can be thrown away after testing is done.

Out the gate, the best reasons for me to use Docker is being able to run a production like environment locally and being able to instantly create new test environments without having to go through the tiring dance of manual configuration. If you haven’t heard about Docker, catch up.
