Official Docker container images for .NET SDK, ASP.NET Core Runtime, and other .NET components.
dotnet/dotnet-docker is the official repository for Docker container images of the .NET platform. It provides production-ready images for .NET SDK, ASP.NET Core Runtime, and other components, enabling developers to containerize .NET applications consistently. These images solve the problem of environment inconsistency and simplify deployment across different platforms.
.NET developers and DevOps engineers who need to containerize applications using Docker, particularly those deploying to cloud platforms or requiring reproducible builds.
Developers choose these images because they are officially maintained by Microsoft, regularly updated for security and compatibility, and include optimized variants like distroless images for production. They provide a reliable foundation for building and running .NET applications in containers.
Official container images for .NET
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Images are maintained by Microsoft with regular updates aligned with .NET releases and security patches, ensuring long-term reliability and compatibility.
Provides images for Windows, Linux, and macOS, enabling consistent deployment across diverse environments from cloud to embedded systems.
Includes minimal images like Ubuntu Chiseled and Azure Linux distroless, reducing attack surface and improving startup times for production workloads.
Automated rebuilds within 12 hours for critical CVEs and monthly for lower-severity fixes, keeping containers secure without manual intervention.
Distroless images lack shells and package managers, making live debugging and dependency troubleshooting difficult without external tools or alternative image variants.
With numerous variants (SDK, runtime, distroless) and tags, choosing the right image can be overwhelming and error-prone for developers new to .NET containerization.
.NET Framework requires a separate repository (dotnet-framework-docker), adding complexity and fragmentation for teams maintaining mixed .NET environments.
Security and performance are tied to upstream base images like Debian or Windows, which may introduce vulnerabilities or bloat beyond .NET's control.