this post was submitted on 15 Feb 2024
352 points (100.0% liked)

196

16591 readers
2705 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
 

silly judgemental post not meant to be taken too seriously (unless you agree with me in which case im dead serious)

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 9 months ago (1 children)

Thank you! I was secretly hoping someone might have a quick suggestion of something to try. I'll see what I can find out.

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

Yeah no problem! My workaround solution is simply just restarting the postgres container when i notice ram usage spiking

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

Usually by the time I notice the server is already unreachable over SSH but I've been considering adding manual healthchecks to my containers. Paired with the docker-autoheal project it's been a really low effort way for me to keep services healthy without a lot of babysitting. I'm more nervous about implimenting it for something like a stateful database though, but I suppose it's no different than manually issuing a docker restart command.