All 16 Docker & Containerization questions
More in Docker & Containerization
What are the official .NET Docker base images, and what's the difference between the sdk, aspnet, and runtime image variants? What is the difference between an image and a container in Docker terminology, applied to a .NET application? How does a multi-stage Dockerfile reduce the final image size for a .NET application, and what does each stage typically do? Why is it recommended to run a containerized .NET application as a non-root user, and how do you configure this in a Dockerfile? What is Docker Compose, and how does it simplify running a multi-container .NET application locally (e.g., API + database + Redis)? How do you pass environment-specific configuration into a running .NET container, and how does this interact with the configuration system? How does .dockerignore improve Docker build performance and image cleanliness for .NET projects? How do you configure a .NET application inside a container to listen on the correct port, and what does ASPNETCORE_URLS control? Why does copying only the .csproj file before the rest of the source code in a Dockerfile improve build caching? What is Native AOT's benefit for containerized .NET applications specifically, beyond the general startup time improvement?
Advertisement
Back to results for “Memory Management”
.NET › Docker & Containerization

How do you configure a .NET container to respect memory and CPU limits set by the container orchestrator (like Kubernetes resource limits)?

Intermediate

Answer

Modern .NET automatically detects container memory and CPU limits (via cgroup information on Linux) and configures the garbage collector and thread pool accordingly by default -- the GC scales its heap size targets based on the container's memory limit rather than the host machine's total memory, and the thread pool sizes itself based on the container's CPU limit (not the host's core count), preventing the classic problem of a containerized app assuming it has access to the entire host's resources.
# Kubernetes resource limits automatically respected by the .NET runtime:
resources:
  limits:
    memory: "512Mi"
    cpu: "1"
# .NET's GC targets a heap size appropriate for 512Mi, not the node's full memory
Real-world example Before this automatic detection was reliable, a team had to manually set DOTNET_GCHeapHardLimit to prevent their containerized app's GC from assuming it had access to the entire host's 64GB of RAM, causing OOM-killed pods under memory pressure.

Common follow-ups: How do you override the automatic detection if it doesn't behave as expected?;What environment variables control GC heap limits explicitly?

Memory Management & Garbage Collection;CLR & Runtime
All 16 Docker & Containerization questions