Diun VS swarm-cronjob

Thanks, I used to use it. I moved to using diun to just notify of updates but not apply them though.

https://crazymax.dev/diun/ and docker compose

Similar to Watchtower but without the option to auto-update containers, just notifying is diun. But imo it does that better and more reliable than Watchtower does. You can get notified by Email, Discord, Pushover, Telegram and many more options.

If your apps are container images, then there are tools like diun, watchtower and whatsupdocker, those can watch the image repository (like Docker Hub) and notify you if a new/updated image has been found. Some can even download and auto-update for you, but that comes at some risk of course.

You might want to have a look at https://crazymax.dev/diun/ which is purpose built for what you're trying to do (notify when an update is available, but not install).

Watchtower is inferior to a project like DIUN this way. Because with double you can actually be notified by newer image versions and act accordingly. But automatic updates (which latest is aswell) are bad practice.

diun is very similar to that, but it doesnt auto-update, just notifies but does that very well imo.

I use https://crazymax.dev/diun/ to send notifications of new images. I also hook it into webbooks with CI for mirroring images, but you should be able to use something like portainer webhooks to auto pull images.

Anything from simple crontab entry to something like this: https://crazymax.dev/swarm-cronjob/

So, I found a really nice little tool that solves a problem I have in a really nice way. Specifically, cron jobs on Docker Swarm. This project: https://github.com/crazy-max/swarm-cronjob It uses labels on your services to schedule jobs. Thus it needs access to the docker api, and all the security concerns that go along with it...

As i said, if it's not exposed to the outside world and doesn't work with untrusted data, that claim is not entirely valid.

Imagine something like this getting abandoned, or someone running a year old version of it: https://github.com/crazy-max/swarm-cronjob/blob/master/READM...

Its only job is to run containers on a particular schedule, no more no less. There are very few attack vectors for something like that, considering that it doesn't talk to the outside world, nor processes any user input data.

Then again, it's not my job to pass judgement on situations like that, merely acknowledge that they exist and therefore the consequences of those suddenly breaking cannot be ignored.

I also found swarm-cronjob and ofelia both seems promising. BUT , I really like the idea of an interface to watch log files etc.