All the .NET Core Opsy Things
Part 1: Choosing the right .NET core Image for your workload Bill 7 min read · 3 days ago 3 days ago -- Listen Share
This guide began as a conversation between me and someone exploring how to containerize .NET apps. The same questions kept coming up; from new developers to infrastructure and DevOps engineers and I kept pointing people to the docs. I decided to turn it into a practical walk through and post it here for anyone who finds it useful.
When you pull an image from mcr.microsoft.com/dotnet/* , you’re getting more than a runtime; you’re pulling from a carefully layered set of container images, each designed to be lightweight, secure, and purpose-built.
Understanding these layers makes it easier to troubleshoot, secure, optimize performance, and pick the right image for your use case.
Image Families
.NET container images are organized into families. Each serves a different job: running, building, hosting web apps, or acting as a base for self-contained apps.
Each family builds on the one below it, adding only what’s needed. That layering impacts size and what’s included by default.
Container Image Size vs Image Family
Sizes are uncompressed and taken directly from docker image ls .
... continue reading