this post was submitted on 19 Apr 2025
19 points (91.3% liked)

Selfhosted

46322 readers
593 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.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
19
Question About Watchtower (lemmy.world)
submitted 1 week ago by [email protected] to c/[email protected]
9 comments fedilink hide all child comments
 

So, I finally installed Watchtower to auto update my containers. I was a little hesitant because just letting apps auto update kind of makes me a little nervous. Even Windows updates give me bouts of trepidation. Everything went well, there was a little hiccup with Netdata but resolved in less than 5 minutes.

My question is that there are four remaining containers that haven't been updated: Speedtest Tracker, Portainer, Doppler Task, and Dockge.

2025-04-19T06:00:46.510622594Z INFO[38092] Session done                                  Failed=0 Scanned=48 Updated=0 notify=no
2025-04-19T08:00:46.040690535Z INFO[45292] Session done                                  Failed=0 Scanned=48 Updated=0 notify=no
2025-04-19T10:00:45.952863778Z INFO[52492] Session done                                  Failed=0 Scanned=48 Updated=0 notify=no
2025-04-19T12:00:47.755915129Z INFO[59694] Session done                                  Failed=0 Scanned=48 Updated=0 notify=no
2025-04-19T14:00:50.046498408Z INFO[66896] Session done                                  Failed=0 Scanned=48 Updated=0 notify=no

Is this indicative of an issue? Do I just need to update these four manually or will Watchtower eventually update them?

Additionally, has anyone ever had any problems with auto updating? It does make me a bit nervous, however I think I will get used to relying on Watchtower.

top 9 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 6 days ago (1 children)

Auto updates can cause problems. Some recommend it, some tell you to not do it. My standpoint is, when a container can't work with auto updates, they suck. Sure there are containers who require some additional attention after an update, like gitea with some config changes but I use it in an environment where it can be offline of some time.

If a container uses Postgresql, you can't auto update. So far I didn't found a well maintained container, that can do this. You also should keep an eye on your containers. As I mentioned, Gitea had some config changes, breaking the default theme (nothing major). They even screwed up their tags and I had 3 times an RC in a tag where no RC should get published. With Jellyfin I was on a tag that didn't got any updates anymore and I needed to use a different one.

[–] [email protected] 1 points 6 days ago (1 children)

If a container uses Postgresql, you can’t auto update.

That's interesting. I certainly will keep that in mind.

[–] [email protected] 2 points 5 days ago

To be more specific: Postgresql requires manual steps with major versions. Tutorials I found require you to dump the database in the old version first, then update and then import. You could use a tagged version of postgresql and just auto update there but the main container might require a newer version. I saw containers who try this but none looked production ready.

[–] [email protected] 3 points 1 week ago (1 children)

What do the logs say?

[–] [email protected] 2 points 1 week ago (1 children)

These are the Watchtower logs so far. https://pastes.io/watchtower

I didn't see anything remarkable other than the error for Netdata but I got that fixed:

NFO[30906] Found new netdata/netdata:latest image (6376ffeda44a) 
INFO[30940] Stopping /NETDATA (a18a3e3409f3) with SIGTERM 
INFO[30942] Creating /NETDATA                            
ERRO[30942] Error response from daemon: the container-wide MAC address must match the endpoint-specific MAC address for the main network, or be left empty
[–] [email protected] 7 points 1 week ago (1 children)

You're being rate limited by Docker Hub. Give it some time and they'll all get updated. Maybe tweak your settings so not everything is attempting an update at the same time.

[–] [email protected] 3 points 6 days ago (1 children)

Thought I had answered you this morning, but apparently not. I did see the rate limit entry, but I thought that rate limits are like 100 pulls every 6 hours and I certainly haven't exceeded 100. I just checked tho, and all but two have updated, so as you say, it'll eventually get around to it. Thank you for the input.

[–] [email protected] 2 points 6 days ago

👍

[–] [email protected] 3 points 1 week ago

It's likely those images haven't been updated in the 8 hour period in which watchtower checked. Daily or weekly update schedule should suffice.