How is .Net Core runtime serviced when hosting in docker containers?

Question

It's clear how the .Net Core runtime is serviced when deploying (shared framework deployment) to a "regular" hosting environment (e.g. azure app service). But how does this work with Docker containers? After all, the .Net runtime is part of the container image which I build and supply to the hosting environment.

Answer 1

Hi @Andriy ,

The way .NET Core runtime is deployed to a regular hosting environment as you mentioned is the same way it's deployed to a Docker container. The main difference being .NET Core, or any framework for that matter, is installed and configured in the Dockerfile image.

There are a host of docker images already setup with .NET Core that you can find over at https://hub.docker.com/_/microsoft-dotnet-runtime/ for either Windows or Linux OS based images. You can also see how those images were built on the docker dotnet repo.

If I misunderstood your question about how .NET Core is incorporated into Docker, please comment below.

EDIT: The team will use the repo I mentioned to apply servicing updates. Images tagged with latest will receive these servicing updates which you can observe here. When your docker file is read, the change in the base image (e.g. mcr.microsoft.com/dotnet/runtime:3.1) will be detected and docker will pull the latest image for that tag and rebuild it for you. This same base image update will occur in ACR or Web App for Containers unless you specify not to.

Regards,
Ryan