Received this notification during routine checks:

Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the Unraid forums  More Information

Diagnostics attached. It appears the issue has been corrected even though the error message is persisting, but there is plenty of memory available:

Would appreciate any insight if there is something going on under the hood that I need to address.

brotower-diagnostics-20260913-2143.zip

These are container-level OOMs, not the Unraid host running out of RAM. There's a container with a hard memory limit of exactly 2 G

The application inside that container is spawning/running multiple headless Chrome processes and their combined memory usage exceeds the container's 2 G limit.

Is there a way to identify which container caused it?

Shoudl be. The errors identify container ID 37db5a294684. Run this in the Unraid terminal to show its name and image:

docker ps -a --filter id=37db5a294684 --format 'table {{.ID}}\t{{.Names}}\t{{.Image}}'

That container reached its 2 GiB memory limit, and the kernel killed chrome-headless processes inside it.

If the command returns only the headings, the container may have been removed or recreated since those errors. In that case, post the output of:

docker ps -a --format 'table {{.ID}}\t{{.Names}}\t{{.Image}}'

We can then narrow down which application runs those processes and check its memory limit.

Thank you @JorgeB , it was Linkwarden with the 2G limit; i've updated with increased memory so hopefully this addresses this issue.