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

Self-Hosted Main

502 readers
4 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
[email protected]
3
My docker containers are stopping constantly. (alien.top)
submitted 10 months ago by [email protected] to c/[email protected]
11 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

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 10 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

[–] [email protected] 1 points 10 months ago (1 children)

Journactl doesn't work in unRAID.

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

[–] [email protected] 1 points 10 months ago (1 children)

What do you mean with host self?

[–] [email protected] 1 points 10 months ago

On the host running unraid.

[–] [email protected] 1 points 10 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