this post was submitted on 15 Nov 2023
2 points (75.0% liked)

Self-Hosted Main

515 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
2
Are there any concerns/risks to using Watchtower? (alien.top)
submitted 1 year ago by notdoreen@alien.top to c/main@selfhosted.forum
33 comments fedilink hide all child comments
 

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 are viewing a single comment's thread
view the rest of the comments
[–] Old-Satisfaction-564@alien.top 0 points 1 year ago

I prefer to be there when container ar updated so that I can promptly fix anything that breaks.

I have 2 watchtower instances in a docker-compose, the first container 'watchtower-monitor' uses command: --monitor-only and warns me over gotify about the availability of updates but does not modify anything, the second 'watchtower-once' uses command: --run-once and it is usually inactive since it performs all updates once and than exits. When i am ready to update everything I just docker-compose start watchtower-once container to start the updates.