main scenarios:1 » Images used to develop .NET Core apps » Images used to build .NET Core apps » Images used to run .NET Core apps Why three images? 1 https://docs.microsoft.com/en-us/dotnet/articles/core/docker/building-net-docker-images 2016/10/31 Fukuoka.NET (Fukuten) #4 ʙ.NET Core Partyʙ 4
can you iterate changes, and the ability to debug the changes. The size of the image isn't as important, rather can you make changes to your code and see them quickly. Some of our tools, like yo docker for use in VS Code use this image during development time. 1 https://docs.microsoft.com/en-us/dotnet/articles/core/docker/building-net-docker-images 2016/10/31 Fukuoka.NET (Fukuten) #4 ʙ.NET Core Partyʙ 5
to compile your app. This includes the compiler and any other dependencies to optimize the binaries. This image isn't the image you deploy, rather it's an image you use to build the content you place into a production image. This image would be used in your continuous integration, or build environment. For instance, rather than installing all the dependencies directly on a build agent, the build agent would instance a build image to 1 https://docs.microsoft.com/en-us/dotnet/articles/core/docker/building-net-docker-images 2016/10/31 Fukuoka.NET (Fukuten) #4 ʙ.NET Core Partyʙ 6
you can deploy and start your image. This image is small so it can quickly travel across the network from your Docker Registry to your Docker hosts. The contents are ready to run enabling the fastest time from Docker run to processing results. In the immutable Docker model, there's no need for dynamic compilation of code. The content you place in this image would be limited to the binaries and content needed to run 1 https://docs.microsoft.com/en-us/dotnet/articles/core/docker/building-net-docker-images 2016/10/31 Fukuoka.NET (Fukuten) #4 ʙ.NET Core Partyʙ 7
SDK which includes the .NET Core and Command Line Tools (CLI). This image maps to the development scenario. You would use this image for local development, debugging and unit testing. For example, all the development you do, before you check in your code. This image can also be used for your build scenarios. 1 https://docs.microsoft.com/en-us/dotnet/articles/core/docker/building-net-docker-images 2016/10/31 Fukuoka.NET (Fukuten) #4 ʙ.NET Core Partyʙ 9
applications and it is optimized for running your application in production. It does not contain the SDK, and is meant to take the optimized output of dotnet publish. The portable runtime is well suited for Docker container scenarios as running multiple containers benefit from shared image layers. 1 https://docs.microsoft.com/en-us/dotnet/articles/core/docker/building-net-docker-images 2016/10/31 Fukuoka.NET (Fukuten) #4 ʙ.NET Core Partyʙ 10