this post was submitted on 09 Dec 2025
154 points (99.4% liked)

Selfhosted

53730 readers
457 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I just has the honors of writing a guest article on selfh.st about my ever so slowly evolving project, dockcheck.

top 26 comments
sorted by: hot top controversial new old
[–] tofubl@discuss.tchncs.de 14 points 1 week ago (2 children)

Is this a replacement for Watchtower?

[–] mag37@lemmy.ml 21 points 1 week ago* (last edited 1 week ago) (1 children)

This question is usually asked a lot.

This started as a project to prove that you could check for updates without first pulling every new image to compare against, while that's not why it kept get getting traction my original answer to this question still seems true:

From Watchtower Docs - Arguments

Due to Docker API limitations the latest image will still be pulled from the registry.

And:

Do not pull new images. When this flag is specified, watchtower will not attempt to pull new images from the registry. Instead it will only monitor the local image cache for changes

It's also a different approach. With dockcheck you'd run it and then make the choice what you'll update there and then. Selectively choosing exactly what containers to update at the moment. Or have it completely unattended auto update a selection of images.

With the notifications, you can get notified and then have a sitdown and auto-update what you choose.

It's just different workflows and options.

The upcoming release will also add a new option to backup the image being updated and then autoprune old backups after N days. To allow for easy rollback if a new image breaks.

[–] tofubl@discuss.tchncs.de 4 points 1 week ago (2 children)

Thanks for the detailed explanation. Will try to see how it fits my setup when I get a chance, but I have been wanting to move away from Watchtower as it is no longer maintained. Good to know there is an alternative, and from what you describe I like your approach. Having to opt-out of updates in Watchtower never really sat right with me- Watchtower clutter is okay in compose files that actually want something to do with Watchtower...

[–] mag37@lemmy.ml 3 points 1 week ago

Thank you. I hope you can find some usefulness in it. You can also do things by compose labels. As well as dynamically at runtime. Either interactively or as arguments.

[–] irmadlad@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

Watchtower as it is no longer maintained

Not to take away anything from the OP, but there is a fork of Watchtower that is maintained and works a lot better than the OG Watchtower. The original Watchtower would screw up the update fairly regularly. So, if you want to just yolo your updates, that'd be the way to go. If you want a bit more control, DockCheck seems to have that covered. It's always good to have choices.

https://watchtower.devcdn.net/

[–] madcaesar@lemmy.world 5 points 1 week ago (3 children)

Watchtower hadn't been updated in like 3 years or something. It's a dead project.

[–] xcjs@programming.dev 2 points 1 week ago

There's a maintained fork, fortunately!

https://github.com/nicholas-fedor/watchtower

[–] Evotech@lemmy.world 2 points 1 week ago (2 children)

What more does it need to do

It works prefectly

[–] madcaesar@lemmy.world 6 points 1 week ago (2 children)

Stopped working for me with a recent docker cli update. That's how I even found out it's totally abandoned.

I'm not a big fan of running software that has access to the internet once it's abandoned like this.

[–] xcjs@programming.dev 1 points 1 week ago

Sorry for spamming in this thread, but if you rely on Watchtower, there's a maintained fork I recommend: https://github.com/nicholas-fedor/watchtower

[–] Evotech@lemmy.world -1 points 1 week ago* (last edited 1 week ago) (1 children)

Is used by literal millions. I'm sure if there was a security issue or would be reported.

Changes for the reason of making changes doesn't make sense either

Anyway, I use podman now. It had this functionality built in

[–] madcaesar@lemmy.world 3 points 1 week ago (1 children)

How many people use it makes no difference if there is no devs fixing security bugs.

I switched to DIUN, but it doesn't do updates only notifications. That's why I'm excited to look at OP's library.

[–] Evotech@lemmy.world 0 points 1 week ago* (last edited 1 week ago)

Are there security issues reported? Is open source

[–] xcjs@programming.dev 1 points 1 week ago

Not for the latest and future versions of Docker.

This fork works, though: https://github.com/nicholas-fedor/watchtower

[–] tofubl@discuss.tchncs.de 0 points 1 week ago (1 children)

Your point being that I am not currently using it? Or that I should be looking for alternatives since I am currently using it?

[–] madcaesar@lemmy.world 0 points 1 week ago

I used to use it and switched away because it's not maintained and I had errors with recent docker cli

[–] uninvitedguest@piefed.ca 6 points 1 week ago

I absolutely adore dockcheck. Thank you for your work.

[–] northernlights@lemmy.today 4 points 1 week ago (1 children)

Oh that's neat, really liking the matrix notifications. Now to make it a systemd service on all my hosts.

[–] mag37@lemmy.ml 2 points 1 week ago (1 children)

Oh nice, yeah I havn't thought about suggesting a systemd-service thats neat! If you'd like you could contribute it as a discussion/suggestion/PR if you land on liking it, thatd be lovely.

With the image backups in the next release you could maybe even build some kind of auto rollback functionality.

[–] northernlights@lemmy.today 1 points 1 week ago (1 children)

Sure I can do that. I make packages too, would you think your project could use AUR, deb, rpm and/or snap packages?

[–] mag37@lemmy.ml 1 points 1 week ago

Oh that's very kind of you! There's an AUR package and a brew already, don't know if other packages is necessary tbh :)

Though some people have suggested they'd like a docker container - which I should try to spend some time on in the future.

[–] HairyHarry@lemmy.world 3 points 1 week ago

Perfect and just what I needed!

[–] domi@lemmy.secnd.me 2 points 1 week ago (2 children)

Does this check for version tags as well or only updates to the current tag?

Like the current container uses an image with the tag :0.1.0 or :v0.1.0 but :0.2.0 is available on the registry.

[–] mag37@lemmy.ml 3 points 1 week ago

Sadly no, only within the scope of the tag specified in the compose.

Renovate, WUD or Diun might be other options for that!

[–] MangoPenguin@lemmy.blahaj.zone 1 points 1 week ago* (last edited 1 week ago) (1 children)

If you want automatic updates over major versions most containers will use the :latest tag for that.

[–] domi@lemmy.secnd.me 3 points 1 week ago

I don't really want automatic updates, I want a notification once a month with all images that have a newer :latest available or if versionised, when a image with a newer version is available.