To be fair, any kind of automated system can just break. So many factors come into play. Azure build pipelines for instance just sometimes decide they can’t communicate with their own servers, causing a build failure.
Comment on Self-Host Weekly #150: Watchtower No More
irmadlad@lemmy.world 2 days agoMy issue was that Watchtower would sporadically just fumble the update, making re-deployment sometimes necessary. It wasn’t a tag issue. At least none that I could see. Of course, the possibility exists that I could just very well be a dumbass. I just assumed that to be the Docker updates that have happened over the past year, and, without any new code, it just broke. It happens.
I either read somewhere or someone tipped me off to the fork. I can only speak for my network, but the fork did the trick. Have had zero issues, and I’ve been using it for a good while. Now, I notice that Watchtower fork hasn’t been updated in 6 months. I guess it’s either been abandoned again or there just hasn’t been a need to do so.
KairuByte@lemmy.dbzer0.com 2 days ago
irmadlad@lemmy.world 2 days ago
Sure. It wasn’t a dig against OG Watchtower, it was just that it ceased to work correctly for me, and I sought other options. Whomever produces selfh.st does have a bit of sarcastic wit to his writing that I kind of like anyways. When speaking about GitHub, he threw out another zinger: ‘Cue the intense backlash from users who hate paying for things’. So, I just think it is his writing style. I didn’t get all hung up on it.
ikidd@lemmy.world 2 days ago
Someone linked this fork, seems maintained:
github.com/nicholas-fedor/watchtower
pulsewidth@lemmy.world 2 days ago
I’ve used it several months and can recommend it. No issues so far and seems to get regular updates for bugfixes and minor new features.
irmadlad@lemmy.world 2 days ago
Hey thank you very much for the tip. I have bookmarked it. I feel better knowing it is going to be maintained.