Maybe there’s something I’m missing here, but it looks my options are to keep a docker on latest, or to pin it to a specific version. It’s great and provides a ton of visibility.Ĭontrast that to managing updates for Dockers in unRaid. You can configure this with various levels of automation, like auto-merging patch and minor versions while holding major versions for review. The gist of how it works is, you pin all of your dependencies, and when there is a new version available, it will open a pull request with the relevant change log, so you can review the updated docs, the code itself, run tests against it, and then make changes before merging if necessary. To help manage this we use a great Github bot called Renovate. So for some context here I’m a JS web developer in my day-to-day, and if anyone is familar with Javascript you know that projects can contain an utter quagmire of dependencies. I have an idea of what I want so I’d like to describe it and see if there actually exists an out-of-the-box solution that I’m unaware of, and if not, if anyone else has experienced this pain point and has advice/interest in a custom-built solution. Hey folks, been running my unRaid server for about a year now, and after a couple of times having Dockers break due to changes in new container versions (one of which resulted in my backups not running for a few weeks), I’m looking for a better system for managing updates.
0 kommentar(er)
