I used to simply use the ‘latest’ version tag, but that occasionally caused problems with breaking changes in major updates.

I’m currently using podman-compose and I manually update the release tags periodically, but the number of containers keeps increasing, so I’m not very happy with this solution. I do have a simple script which queries the Docker Hub API for tags, which makes it slightly easier to find out whether there are updates.

I imagine a solution with a nice UI for seeing if updates are available and possibly applying them to the relevant compose files. Does anything like this exist or is there a better solution?

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

    Ideally containers are provided with a major release version tag, so not just :latest but :0.18 for all 0.18.x releases that should in theory not break compatibility.

    Then you can set your Podman systemd configuration file (I use Quadlet .container files) to automatically check for new versions and update them.

      • exu@feditown.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Well, most projects publish their dockerfiles so you could take ans rebuild them with the tags you want. And all the building can be built into a CI/CD pipeline so you just have to make a new push with the latest versions.

        I should make something like that.

    • Leafimo@feddit.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      this is the way to do it.

      and periodically keep taps on main releases to swap from 0.18 to 0.19