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?

  • DH10@feddit.deEnglish
    7·
    1 year ago

    I don’t like the auto update function. I also use a script similar to the one op uses (with a .ignore file added). I like to be in control when (or if) updates happen. I use watchtower as a notification service.

    • Mythnubb@lemm.eeEnglish
      1·
      1 year ago

      Exactly, when it updates, I want to initiate it to make sure everything goes as it should.

      • pete_the_cat@lemmy.worldEnglish
        1·
        1 year ago

        Nothing off mine is that important that I couldn't create/rollback the container if it does happen to screw up.

    • chiisana@lemmy.chiisana.netEnglish
      1·
      1 year ago

      I scream test myself… kidding aside, I try to pin to major versions where possible — Postgres:16-alpine for example will generally not break between updates and things should just chip along. It’s when indie devs not tagging anything other than latest or adhere to semantic versioning best practices where I keep watchtower off and update once in a blue moon manually as a result.