For the last two years, I’ve been treating compose files as individual runners for individual programs.

Then I brainstormed the concept of having one singular docker-compose file that writes out every single running container on my system… (that can use compose), each install starts at the same root directory and volumes branch out from there.

Then I find out, this is how most people use compose. One compose file, with volumes and directories branching out from wherever ./ is called.

THEN I FIND OUT… that most people that discover this move their installations to podman because compose works on different versions per app and calling those versions breaks the concept of having one singular docker-compose.yml file and podman doesn’t need a version for compose files.

Is there some meta for the best way to handle these apps collectively?

  • krolden
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    Podman with systemd works better if you just do your podman run command with all the variables and stuff and then run podman generate systemd.

    Podman compose feels like a band aid for people coming from docker compose. If you run podman compose and then do podman generate systemd, it will just make a systemd unit that starts podman compose. In my experience having all of the config stuff in the actual systemd unit file makes your life easier in the long run. Fewer config files the better I say.

    • poVoq@slrpnk.net
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      It’s even simpler now that Quadlet is integrated in Podman 4.x or later.

      • krolden
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Oh yeah I remember reading some stuff about that but didn’t dig too deep. I’ll have to check it out again