I dont see anything in the container logs and I dont know what could it be
You must log in or register to comment.
Most likely low memory, linux systems when there are out of memory calls the OOM killer, which kills the largest processes running on the system. https://unix.stackexchange.com/questions/153585/how-does-the-oom-killer-decide-which-process-to-kill-first
You can probably find evidence of this in the system logs, on most modern systems, this should show you higher prio logs from last boot:
journalctl -p 4 -bYou should see something like this, if it was killed by OOM killer
MESSAGE=Killed process 3029 (Web Content) total-vm:10206696kB, anon-rss:6584572kB, file-rss:0kB, shm em-rss:8732kBAnd you should definitely think about extending the memory of the system or reducing the number of containers/they memory footprint.
You can also see oom killer messages with dmesg
Journactl doesn’t work in unRAID. I don’t thinks it’s a memory problem usually memory usage is around 10-15GB and I have 40gb of memory
Journactl doesn’t work in unRAID.
So do the
journalctl -p 4 -bon the host self.What do you mean with host self?
On the host running unraid.
The question is not so much if you have enough physical ram but if your docker management tool has established resource limits for the containers. Oom killer will stop the process regardless of the fact that there is enough free memory if the container goes over its Ressource contraints.
Maybe memory limits of some kind ? you can set the maxium memory usage in a docker compose file for example!
always put limits on containers !
i.e.
services: qbittorrent: container_name: qbittorrent cpus: 1 mem_limit: 1g environment:I thought limits only worked in swarms?
Really not enough information to go on here. I’m not familiar with unraid, but can you add
restart: alwaysto the compose file for these containers? Does it have a compose file?If you’re sure it’s not a memory issue (and it would be a bit odd for the OOM-kill to kill a bunch of containers like this), it could be an IO issue. A hard drive dying, maybe, but I think unraid should let you know about that?