advancedTop 100 Interview Questions

Why is it risky to set no memory limit on a production container?

Without a memory limit (cgroup constraint), a container with a memory leak or unexpectedly high load can consume all available host memory, starving other containers on the same host and potentially triggering the kernel's OOM killer to terminate arbitrary processes rather than just the offending one in a controlled way.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full DevOps Mastery library.

Why is it risky to set no memory limit on a production container?

Next Step

Continue to What's the difference between `docker run --memory` and a Kubernetes Pod's resource `limits`/`requests`?← Back to all Docker questions