.NET 10.0 Container Images Now Available

[lbussell]

.NET 10.0 is now generally available.

• docker pull mcr.microsoft.com/dotnet/sdk:10.0
• docker pull mcr.microsoft.com/dotnet/runtime:10.0
• docker pull mcr.microsoft.com/dotnet/aspnet:10.0

Release notes:

• Blog Post: Announcing .NET 10
• What's new in .NET 10
• Breaking changes in .NET 10

Container image platforms available at launch

Linux

• Ubuntu 24.04 "Noble" (10.0, 10.0-noble, 10.0-noble-chiseled)
• Alpine Linux 3.22 (10.0-alpine, 10.0-alpine3.22)
• Azure Linux 3.0 (10.0-azurelinux3.0, 10.0-azurelinux3.0-distroless)

Windows

• Nano Server 2025 (10.0-nanoserver-ltsc2025)
• Nano Server 2022 (10.0-nanoserver-ltsc2022)
• Windows Server Core 2025 (10.0-windowsservercore-ltsc2025)
• Windows Server Core 2022 (10.0-windowsservercore-ltsc2022)

New versions of these OSes will be added throughout .NET 10's support lifecycle according to the .NET containers supported platforms policy. For full tag listings, see the individual image repo readmes:

• dotnet/sdk: .NET SDK
• dotnet/aspnet: ASP.NET Core Runtime
• dotnet/runtime: .NET Runtime
• dotnet/runtime-deps: .NET Runtime Dependencies
• dotnet/monitor: .NET Monitor Tool
• dotnet/monitor-base: .NET Monitor Tool

Changes for .NET 10 container images

Ubuntu images are now the default

The default Linux distro for .NET tags has been changed from Debian to Ubuntu. This applies to all .NET tags that do not explicitly specify an OS.

• docker pull mcr.microsoft.com/dotnet/sdk:10.0 - Refers to Ubuntu 24.04 "Noble Numbat"
• docker pull mcr.microsoft.com/dotnet/sdk:10.0-noble - Refers to Ubuntu 24.04 "Noble Numbat"

Ubuntu Chiseled images now contain the Chisel manifest

Ubuntu Chiseled images are a type of distroless container image that contain only the minimal set of packages .NET needs, with everything else removed. New for .NET 10, Ubuntu Chiseled images include the Chisel manifest.
The Chisel manifest describes the package contents of the image and can also be used to install additional packages on top of existing Chiseled base images.

Ubuntu Chiseled base images:

• docker pull mcr.microsoft.com/dotnet/aspnet:10.0-noble-chiseled
• docker pull mcr.microsoft.com/dotnet/runtime:10.0-noble-chiseled
• docker pull mcr.microsoft.com/dotnet/runtime-deps:10.0-noble-chiseled

Other image variants are also available. For more information, see:

• How do I install additional packages on Chiseled images?
• Chisel manifest documentation
• PR: Add documentation for installing additional slices on Ubuntu Chiseled images (dotnet/dotnet-docker#6187).

Native AOT SDK images

Native AOT .NET apps have faster startup time, smaller memory footprints, and can run on machines that don't have the .NET runtime installed.

For .NET 10, we are publishing new .NET SDK image variants that support building Native AOT apps.

The images are intended for two primary scenarios:

• Building container images that contain a Native AOT app, using the SDK image in a multi-stage Dockerfile
• Building Native AOT .NET executables using the SDK image as a containerized build environment

See the .NET Native AOT Dockerfile samples for details on how to use the new Native AOT SDK images.

The following images have been added to the dotnet/sdk repo:

• docker pull mcr.microsoft.com/dotnet/sdk:10.0-noble-aot (Also tagged as 10.0-aot)
• docker pull mcr.microsoft.com/dotnet/sdk:10.0-alpine-aot
• docker pull mcr.microsoft.com/dotnet/sdk:10.0-azurelinux3.0-aot

For more information, see:

• .NET 10 SDK AOT container images (Announcement)
• Provide Officially-Supported .NET AOT Images

dnx is now on the PATH in SDK images

dnx is now available directly from .NET 10 SDK container images. See One-shot tool execution for more details about dnx.

To run a .NET tool using dnx in your Dockerfile build, you can use the following syntax:

FROM mcr.microsoft.com/dotnet/sdk:10.0
RUN dnx --yes <packageId> [<commandArguments>...]

To use dnx from the .NET SDK image directly from the command line, you can use the following Docker command:

docker run --rm mcr.microsoft.com/dotnet/sdk:10.0 dnx --yes <packageId> [<commandArguments>...]