.NET SDK
This image contains the .NET SDK which is comprised of three parts:
- .NET CLI
- .NET runtime
- ASP.NET Core
Use this image for your development process (developing, building and testing applications).
Watch discussions for Docker-related .NET announcements.
9.0
(Standard Support)docker pull mcr.microsoft.com/dotnet/sdk:9.0
8.0
(Long-Term Support)docker pull mcr.microsoft.com/dotnet/sdk:8.0
.NET:
- dotnet: .NET
- dotnet/aspnet: ASP.NET Core Runtime
- dotnet/runtime: .NET Runtime
- dotnet/runtime-deps: .NET Runtime Dependencies
- dotnet/monitor: .NET Monitor Tool
- dotnet/aspire-dashboard: .NET Aspire Dashboard
- dotnet/nightly/sdk: .NET SDK (Preview)
- dotnet/samples: .NET Samples
.NET Framework:
- dotnet/framework: .NET Framework, ASP.NET and WCF
- dotnet/framework/samples: .NET Framework, ASP.NET and WCF Samples
The .NET Docker samples show various ways to use .NET and Docker together. See Building Docker Images for .NET Applications to learn more.
Building .NET Apps with Docker
- .NET Docker Sample - This sample builds, tests, and runs the sample. It includes and builds multiple projects.
- ASP.NET Core Docker Sample - This sample demonstrates using Docker with an ASP.NET Core Web App.
Develop .NET Apps in a Container
The following samples show how to develop, build and test .NET applications with Docker without the need to install the .NET SDK.
- Build .NET Applications with SDK Container
- Test .NET Applications with SDK Container
- Run .NET Applications with SDK Container
.NET container images have several variants that offer different combinations of flexibility and deployment size. The Image Variants documentation contains a summary of the image variants and their use-cases.
Lifecycle
Image Update Policy
- Base Image Updates: Images are re-built within 12 hours of any updates to their base images (e.g. debian:bookworm-slim, windows/nanoserver:ltsc2022, etc.).
- .NET Releases: Images are re-built as part of releasing new .NET versions. This includes new major versions, minor versions, and servicing releases.
- Critical CVEs: Images are re-built to pick up critical CVE fixes as described by the CVE Update Policy below.
- Monthly Re-builds: Images are re-built monthly, typically on the second Tuesday of the month, in order to pick up lower-severity CVE fixes.
- Out-Of-Band Updates: Images can sometimes be re-built when out-of-band updates are necessary to address critical issues. If this happens, new fixed version tags will be updated according to the Fixed version tags documentation.
CVE Update Policy
.NET container images are regularly monitored for the presence of CVEs. A given image will be rebuilt to pick up fixes for a CVE when:
- We detect the image contains a CVE with a CVSS score of "Critical"
- AND the CVE is in a package that is added in our Dockerfile layers (meaning the CVE is in a package we explicitly install or any transitive dependencies of those packages)
- AND there is a CVE fix for the package available in the affected base image's package repository.
Please refer to the Security Policy and Container Vulnerability Workflow for more detail about what to do when a CVE is encountered in a .NET image.
Feedback
- Legal Notice: Container License Information
- .NET license
- Discover licensing for Linux image contents
- Windows base image license (only applies to Windows containers)
- Pricing and licensing for Windows Server