38
Keeping .yaml files up to date... (piefed.social)
submitted 11 months ago by to c/selfhosted@lemmy.world
32 comments fedilink hide all child comments
 

For those of you that use docker, how do you make sure your docker-compose.yml (and possibly .env) files stay current with the project's ongoing updates? I'm sure there's an easier way than what I'm doing which is manually getting the latest ones and checking the diffs in vscodium. And I'm sure some git magic already takes care of this but I've been slow in learning git beyond the VERY basics. Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 11 months ago (4 children)

I have automatic updates through a watchtower fork, so I just leave it alone until it breaks, then I go to the project site to see what changed. This has happened maybe twice in the last couple years.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 2 points 11 months 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 11 months ago (2 children)

    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))

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 11 months ago* (last edited 11 months ago) (1 child)

    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 update on again. I'll stick to this until checking updates is less work than fixing the occasional problem

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 11 months 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

  • permalink
  • fedilink
  • source
  • parent