2y ago

Are there any concerns/risks to using Watchtower?

Someone recommended it for keeping my containers up to date automatically. I checked out the repo and it seems too good to be true. It just updates your containers when a new image is available and everything just works out of the box? I'm a bit scared of just leaving it alone in case it might break something. The fact that it doesn't come with a gui also scares me a bit.

Does anyone here use it and can recommend it? Any horror stories?

You're viewing a single thread.

33 comments

If you want highly available system, then you should perform updates with a custom made script, where you can control update issues. Otherwise watchtower is good.
- Curious how a custom script to perform the update would be different than watchtower doing it? Is an automated update not an automated update regardless of what triggers it?
- If you have a script like this any chance you could open source it?
  
  My script looks like this: https://gist.github.com/dgalli1/010fb978bae509dda43a1f31145a530f
  And is ment to update docker-compose.yml files.
  
  Great script! Only thing I can recommend is adding a "docker image prune -af" command after all compose files have had new images pulled and are up…unless you want old images taking up hard drive space/you have a valid reason for keeping old images.
  
  If you want to have zero downtime, you can scale the container to two and if everything succeeded just kill the old container. (Need reverse proxy with balancing like caddy)
  
  You understand that at the point where they open source it and publish it it would be essentially watchtower right? The point of having a custom-made script is so that you can customize it to your specific needs if it's a generalized item then just use watchtower.

33 comments