this post was submitted on 11 Sep 2026
10 points (69.2% liked)

Selfhosted

62068 readers
633 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I built Versentry to scratch my own itch: I run Docker across several self-hosted boxes and wanted to know when images have updates - without anything auto-pulling or restarting my containers behind my back.

Before that, I used WUD, but at the time Versentry was created, it didn’t have a proxy for Telegram notifications, which was the impetus. As a result, I ended up with a micro‑service that fully meets my needs.

What it does: reads running containers from the local Docker socket, compares their tags and digests against OCI registries, and sends a notification when something's newer. It never pulls images or touches containers. That's the whole point - notify-only by design.

A few things that set it apart:

  • Central tag-filter rules in config (regex by image repo), so you're not forced to label every container. Per-container versentry.include labels also work if you prefer them.
  • Built-in proxy (SOCKS5/HTTP) for notifier delivery and registry traffic - handy behind network restrictions.
  • Any OCI registry - Docker Hub, GHCR, Quay, GitLab out of the box; private/self-hosted via type: oci.
  • Notifiers: stdout, Telegram, Discord, Gotify, ntfy, and a generic webhook.
  • Readable notifications out of the box - sensible default messages, no template-wrangling required; Go text/template overrides are there if you want to customize.
  • semver/numeric detection (cross-major updates get flagged) plus digest comparison for floating tags like latest.
  • Tiny ~5 MB scratch-based image, MIT licensed.

It's probably not for you if you need: a web UI (try WUD), automatic pull-and-restart (that's Watchtower's job), non-Docker providers like Kubernetes/Podman (Diun covers more), or Slack/email as first-class notifiers.

It's a young project - fewer battle-tested deployments than the established tools - so I'd genuinely welcome feedback from anyone who runs it.

GitHub: https://github.com/BlackRaincoat/versentry

AI Disclosure:

  • Design - Pair
  • Implementation - Generated
  • Testing - Assisted
  • Documentation - Generated
  • Review - Assisted
  • Deployment - Generated

Note: The idea, the architecture decisions, and all real-world testing were mine - I ran it across multiple live servers and that's what caught the actual bugs. The AI wrote the implementation, the test code, docs, and CI config from my prompts. I reviewed behavior on real deployments rather than reading every line, so code-level review leaned on the AI.

you are viewing a single comment's thread
view the rest of the comments
[–] BlackRaincoat@lemmy.world 1 points 12 hours ago

Thanks, that's a genuinely nice way to look at it. The grafana tally is a cool setup - piping update status into the rest of your monitoring makes a lot of sense. I'll definitely poke at dockcheck to see how it does things. Cheers!