I have many services running on my server and about half of them use postgres. As long as I installed them manually I would always create a new database and reuse the same postgres instance for each service, which seems to me quite logical. The least amount of overhead, fast boot, etc.

But since I started to use docker, most of the docker-compose files come with their own instance of postgres. Until now I just let them do it and were running a couple of instances of postgres. But it’s kind of getting rediciolous how many postgres instances I run on one server.

Do you guys run several dockerized instances of postgres or do you rewrite the docker compose files to give access to your one central postgres instance? And are there usually any problems with that like version incompatibilities, etc.?

  • Moonrise2473
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    I have everything in docker too, but a single yml with 40 services is a bit extreme - you would be forced to upgrade everything together, no?

    • sardaukar@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      Not really. The docker-compose file has services in it, and they’re separate from eachother. If I want to update sonarr but not jellyfin (or its DB service) I can.