• @p_235615B
    link
    fedilink
    English
    38 months ago

    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 -b

    You 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:8732kB

    And you should definitely think about extending the memory of the system or reducing the number of containers/they memory footprint.

  • @traversedaB
    link
    fedilink
    English
    18 months ago

    Really not enough information to go on here. I’m not familiar with unraid, but can you add restart: always to 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?

  • @pigers1986B
    link
    fedilink
    18 months ago

    always put limits on containers !

    i.e.

    services:
        qbittorrent:
            container_name: qbittorrent
            cpus: 1
            mem_limit: 1g
            environment:
    
  • @iluvfitnessmodelsB
    link
    fedilink
    English
    18 months ago

    Maybe memory limits of some kind ? you can set the maxium memory usage in a docker compose file for example!