Selfhosted

38810 readers

132 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Restart an OOM killed docker automatically (lemmy.world)

submitted 1 month ago by [email protected] to c/[email protected]

32 comments fedilink hide all child comments

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

[–] [email protected] 8 points 1 month ago (2 children)

I don't know the best way

Apparently...

Don't do this. Either don't go OOM to begin with (somebody else told you how to limit container memory usage} and/or configure systemd to restart docker if it quits. I'm surprised systemd isn't already.

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago) (1 children)

It's usually good to state why something is good or bad :)

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

It's fairly obvious I feel.

You're saying rather than use a system tool that does the exact thing that you want you should bodge together a cron job that accomplishes your goal but doesn't actually do what you want.

Like say you want to stop the docker service for some reason? systemctl stop docker will do that. Then your cron job will restart it. That's not the desired outcome. You want the service running IF the service SHOULD be running. Which is a different thing than "always running". And its' exactly what you get for free with systemd without any silly custom BS.

[–] [email protected] 1 points 1 month ago (1 children)

Seems like the best solution. I'll look into it

[–] [email protected] 0 points 1 month ago (1 children)

Seems like the best solution.

Over using a system tool designed to monitor and restart services that stop?

[–] [email protected] 1 points 1 month ago (1 children)

? I'm agreeing with you?

[–] [email protected] 1 points 1 month ago

Sorry - was ambiguous and thought you were saying the "cron" thing sounded best.