Comment on Keeping .yaml files up to date...

frongt@lemmy.zip ⁨2⁩ ⁨days⁩ ago

• neonrain@piefed.social ⁨2⁩ ⁨days⁩ ago

  I use a watchtower fork as well to keep some containers updated but I’m curious how others keep on top of docker-compose.yml files that the project updates over time. As an example, I’ve been using a container for years and noticed today that on the github page they’ve added a section in the compose file for a health check. I never would’ve known that was added if I didn’t stumble upon it due to another issue.

  source
• Appoxo@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ ago

  Hope you have backups.
  Broke my neck a few times (I currently am waiting out the jellyfin patches and stay on 10.10.7 (i think))

  source

  • shiftymccool@piefed.ca ⁨1⁩ ⁨day⁩ ago

    Easy, reliable backups are key. I’ve used komodo with automatic updates for over a year and watchtower before that for a couple more. I’ve only had one issue when Nginx Proxy Manager had a release that deleted all of its own data. Didn’t take long to realize that the services were still up and what the problem was. Restored the missing data from Proxmox backups, pinned the Nginx version for a while, then turned auto backup on again. I’ll stick to this until checking updates is less work than fixing the occasional problem

    source

    • Appoxo@lemmy.dbzer0.com ⁨1⁩ ⁨day⁩ ago

      Just a few days ago, my docker host upgraded the docker engine from 28 to 29.
      Woke up to 10 notifications from my uptime monitoring that they are offline.

      Funny thing is: The external monitor showed they are down. The internal monitor showed no issues.

      But after I went through with the long procrastinated upgrade from debian 11 to debian 13, migrating the data and doing nothing to the compose files, all services worked without any issue.
      I don’t know what my old host did or did not but now it works, I guess? Not complaining but the whole routing thing is a bit beyond me

      source