Comment on Docker Hub's trust signals are a lie — and Huntarr is just the latest proof
Kushan@lemmy.world 1 week agoI generally agree with the sentiment but don’t pull by latest, or at the very least don’t expect every new version to work without issue.
Most projects are very well behaved as you say but they still need to upgrade major versions now and again that contains breaking charges.
I spebt an afternoon putting my compose files into git, setting up a simple CI pipeline and use renovate to automatically create PR’s when things update. Now all my services are pinned to specific versions and when there’s an update, I get a PR to make the change along with a nice change log telling me what’s actually changed.
It’s a little more effort but things don’t suddenly break any more. Highly recommend this approach.
CameronDev@programming.dev 1 week ago
That does sound like a good approach. Are you able to share that CI pipeline? I am mostly happy to risk the occasional breakage, nothing is really critical. But something more reliable would probably save me some drama every so often when it does break.
Kushan@lemmy.world 1 week ago
Absolutely! Here’s my CI pipeline, it’s actually super basic: gist.github.com/…/bd92031bb9c8db3320e8c19d5dae319…
Happy to answer questions if you like.
I just added my compose files to the repo, that CI file and set up renovate github.com/renovatebot/renovate to create my PR’s for me.