My server (fedora) stops all podman containers after 2-3 hours since 3 days. I can start all containers again, and the same happens after a while. I do not know where to look for the problem.

In top, I found a oom message. I assume that the system runs out of memory and stops all services. How can I find the problem? I can’t find anything in the container logs.

I can see that systemctl status is always starting. It doesn’t become “running”. But I do not know how to proceed.

    • atzanteol@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      9
      ·
      6 months ago

      If something you’re running has a memory leak then it doesn’t matter how much RAM you have.

      You can try adding memory limits to your containers to see if that limits the splash damage. That’s to say you would hopefully see only one container (the bad one) dying.

      • GravitySpoiled@lemmy.mlOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 months ago

        that’s neat. Tank you.

        So far I follow a bottom up strategy. I’ll keep adding containers each day (or after many hours) and wait for it to stop. I also looked up how to limit memory usage. It’s a great idea to limit all containers and see which one fails. thanks!

    • B0rax@feddit.de
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 months ago

      How do you know that you have too much ram? Have you set up a monitoring solution like influxDB to track ram usage over time?