Comment

Comment on Restart an OOM killed docker automatically

The other person may have responded with a fair amount of hostility, but they're absolutely correct. I run Kubernetes clusters hosting millions of containers across hundreds of thousands of VMs at my job, and OOMKills are just a fact of life. Apps will leak memory, and you're powerless to fix it unless you're willing to debug the app and fix the leak. It's better for the container to run out of memory and trigger a cgroup-scoped OOM kill. A system-wide OOM kill will murder the things you love, shit in your hat, and lick your face like David Tennant licked Krysten Ritter.

source

Sort:hotnew top

RustyNova@lemmy.world ⁨4⁩ ⁨months⁩ ago
Oh that’s not a problem to let a container get killed. It’s perfectly fine. What I want is just not crippling my whole server because one container did a funny.

If it keeps docker and the portainer VM I’ll be 100% ok, because I can just restart it. I don’t want to have remote access to my server outside of my home for security reasons, so this is just the bare minimum

source
- Findmysec@infosec.pub ⁨4⁩ ⁨months⁩ ago
  Those remote access fears can be solved with a wireguard VPN
  
  source
- null@slrpnk.net ⁨4⁩ ⁨months⁩ ago
  
  I don’t want to have remote access to my server outside of my home for security reasons, so this is just the bare minimum
  
  What are your security concerns?
  
  source