this post was submitted on 19 Nov 2023
2 points (100.0% liked)

Self-Hosted Main

21 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
2
My docker containers are stopping constantly. (alien.top)
submitted 11 months ago by gerardit04@alien.top to c/main@selfhosted.forum
10 comments fedilink hide all child comments
 

I dont see anything in the container logs and I dont know what could it be

​

https://preview.redd.it/s00u07iqea1c1.png?width=1812&format=png&auto=webp&s=296fc0ee6eef5542575b8e37cbe20cd1beb82801

top 10 comments
sorted by: hot top controversial new old
[–] p_235615@alien.top 3 points 11 months ago (2 children)

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.

[–] gerardit04@alien.top 1 points 11 months ago (2 children)

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

[–] stappersg@alien.top 1 points 11 months ago (1 children)

Journactl doesn't work in unRAID.

So do the journalctl -p 4 -b on the host self.

[–] gerardit04@alien.top 1 points 11 months ago (1 children)

What do you mean with host self?

[–] mosaic_hops@alien.top 1 points 11 months ago

On the host running unraid.

[–] lilolalu@alien.top 1 points 11 months ago

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.

https://stackoverflow.com/questions/42345235/how-to-specify-memory-cpu-limit-in-docker-compose-version-3

[–] lilolalu@alien.top 1 points 11 months ago

You can also see oom killer messages with dmesg

[–] traverseda@alien.top 1 points 11 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?

[–] pigers1986@alien.top 1 points 11 months ago (1 children)

always put limits on containers !

i.e.

services:
    qbittorrent:
        container_name: qbittorrent
        cpus: 1
        mem_limit: 1g
        environment:
[–] adamshand@alien.top 1 points 11 months ago

I thought limits only worked in swarms?