Microsoft publishes excellent .NET Docker images, but most teams use them incorrectly - shipping the SDK image to production or missing the chiseled variants that cut image size in half. We build .NET containers using the proper SDK/runtime split with chiseled base images, non-root users, and health check endpoints.
Need this done for your project?
We implement, you ship. Async, documented, done in days.
The .NET SDK image is 800+ MB - it includes compilers, NuGet tooling, and debug symbols you never need in production. Yet many teams deploy with FROM mcr.microsoft.com/dotnet/sdk:8.0 because the Dockerfile was copy-pasted from a tutorial.
A proper multi-stage build uses the SDK image for dotnet publish and a runtime-only or chiseled image for the final stage, cutting image size to 80-120 MB and removing the attack surface of build tooling.
Two-stage build using Microsoft's official images:
FROM mcr.microsoft.com/dotnet/sdk:8.0 AS build - runs dotnet restore first (lockfile layer cache), then dotnet publish -c Release -o /app/publish --no-restore with optional -p:PublishTrimmed=true for AOT-compatible apps.FROM mcr.microsoft.com/dotnet/aspnet:8.0-jammy-chiseled - the chiseled variant is a distroless-like Ubuntu image with no shell, no package manager, and non-root by default. Copies published output to /app.Compose file sets ASPNETCORE_URLS=http://+:8080, maps the port, includes a health check against /health, and sets DOTNET_EnableDiagnostics=0 to disable diagnostics in production.
Dockerfile with chiseled runtime image - 80-120 MBdocker-compose.yml with health checks, resource limits, and non-root executiondotnet restore cache and Docker layer cacheSkip the research. Tell us what you need, and we'll scope it, implement it, and hand it back — fully documented and production-ready.