Comment on Restart an OOM killed docker automatically

GravitySpoiled@lemmy.ml ⁨2⁩ ⁨months⁩ ago

• atzanteol@sh.itjust.works ⁨2⁩ ⁨months⁩ ago

  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.

  source

  • RustyNova@lemmy.world ⁨2⁩ ⁨months⁩ ago

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

    source

    • atzanteol@sh.itjust.works ⁨2⁩ ⁨months⁩ ago

      Seems like the best solution.

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

      source

      • RustyNova@lemmy.world ⁨2⁩ ⁨months⁩ ago

        ? I’m agreeing with you?

        source

        • -> View More Comments
  • GravitySpoiled@lemmy.ml ⁨2⁩ ⁨months⁩ ago

    It’s usually good to state why something is good or bad

    source

    • atzanteol@sh.itjust.works ⁨2⁩ ⁨months⁩ 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”.

      source
• RustyNova@lemmy.world ⁨2⁩ ⁨months⁩ ago

  I’ll try that. I know that systemctl has a start-or-reload command, but is there any “start-or-ignore” commands? Or start flags?

  source