Crumb
c/selfhosted · by abies_exarchia@lemmy.dbzer0.com · 292d

Getting the versions of running services for Argus

Hi all, I've been looking for a solution for keeping track of the versions of my docker containers and when they might need updates. I tried cup and cupdate but I didn't feel like I had enough granular control of which docker images were showing up and it was tricky to find github release notes for each release. I found argus which allows more control (indeed, you have to manually configure each service you add) and you essentially scrape github for version numbers and then either scrape your service webpage for a version number or use a service's api for version. This works for a lot of services, and I really like it so far. However, I have no idea how to get version numbers for some services like karakeep or actual. My question is: are there hacky ways that I can expose version numbers from my services, or am I shit out of luck if it's not on the login page or exposed by an API?

Thanks!

10 points · 6 comments · view on lemmy.world

6 Comments

irmadlad@lemmy.world · 3 pts · 292d (2 replies)

There is a Watchtower fork. The older Watchtower has not been updated in two years.

https://watchtower.devcdn.net/container-selection/ By default, watchtower will watch all containers. However, sometimes only some containers should be updated.

There are two options:

  1. Fully exclude: You can choose to exclude containers entirely from being watched by watchtower.
  2. Monitor only: In this mode, watchtower checks for container updates, sends notifications and invokes the pre-check/post-check hooks on the containers but does not perform the update.
abies_exarchia@lemmy.dbzer0.com · 2 pts · 292d (1 reply)

Cool, thanks for the rec! Is there an easy way to view release notes? For cupdate and cup i had to open a new tab and go to the release page myself to see if there were breaking changes or whatever. This became annoying with many services

irmadlad@lemmy.world · 0 pts · 292d

https://github.com/beatkind/watchtower/releases/tag/v2.3.1

frongt@lemmy.zip · 2 pts · 292d (2 replies)

Is it not exposed as an attribute of the container itself in the docker API?

abies_exarchia@lemmy.dbzer0.com · 2 pts · 292d

Y’know, this would make a lot of sense. I can try it! It’s puzzling though that argus wouldn’t have this in their documentation though (I’ve looked)

lucullus@discuss.tchncs.de · 1 pts · 291d

You can get the image SHA. If you then provide the corresponsig tag, that you used, an application could check if a new image is available. Or maybe if you use docker compose, the app could get the tag from the compose file, and even check for new tagged versions based on a specific pattern.