Why might a containerized application behave differently regarding available memory than expected, even with "--memory" not set?
Correct! Well done.
Incorrect.
The correct answer is B) Without an explicit limit, a container can see and potentially use the host's total memory, which can mislead applications (especially JVM-based ones) that auto-tune based on detected available memory, sometimes causing them to over-allocate
Correct Answer
Without an explicit limit, a container can see and potentially use the host's total memory, which can mislead applications (especially JVM-based ones) that auto-tune based on detected available memory, sometimes causing them to over-allocate
Without cgroup memory limits, "/proc/meminfo" inside a container can report the host's total memory, which can cause memory-aware applications to size caches or heaps based on incorrect assumptions about available resources.