this post was submitted on 12 Jul 2024
25 points (83.8% liked)

Selfhosted

40296 readers
212 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.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I got an home server that is running docker for all my self hosted apps. But sometimes I accidentally trigger Earlyoom by remotely starting expensive docker builds, which kill docker.

I don't have access to my server outside of my home network, so I can't manually restart docker in those situations.

What would be the best way to restart it automatically? I don't mind doing a full system restart if needed

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 2 points 4 months ago

Then you didn't explain the issue very well, because what you're asking for was given to you exactly. Builds also have flags, and you should know that if you're complaining about advice given to you. I'm not saying that to admonish you, just giving you the info.

The next step down is that you're using Portainer, and having user-error issues somehow. So another solution is renaming these actions something with a very obvious prefix like "BUILD ACTION", but also setting memory limits.

The very last step is making sure your swap is in order. Allocate 2x your system memory to swap, and this will help alleviate OOM issues to a point, but especially during builds.

If you come back and say this is a band-aid solution, get a better machine and stop asking questions to solve the impossible in here. This is your fault this is an issue to begin with, you don't know how to run your machines (regardless of it just being a home server or whatever ), and you're just being rude.