A container with no memory limit, and the process the kernel kills instead
Set a memory limit, read docker stats and docker inspect to tell a victim of the OOM killer from any other SIGKILL, and recognise the kernel line that says the host ran out rather than the container.
20 minutesTechnical content last reviewed on 13 Sept 2026
This lesson is for signed-in learners
Create an account to subscribe and record your learning progress.
What this lesson builds
- Running an application in containers without losing its data
- Reading system state without over-reading it