3 ms·
What process or processes were you running in the container? Edit: nvm, saw you answered it in another thread: `find / > /dev/null`. Interesting!
by umanwizard 6y ago
What process or processes were you running in the container?
Edit: nvm, saw you answered it in another thread: `find / > /dev/null`. Interesting!
- jeffbee 6y agoYes, find and its parent, the shell, but that's not why it OOMs. It OOMs because Linux uses a lot of memory for inodes and dirents and whatever it puts in slabs and then when memory pressure occurs -- when Linux must allocate in the kernel but cannot, due to limits -- it just loses its mind and instead of reclaiming it kills.