mag37

joined 2 years ago
[–] [email protected] 2 points 7 hours ago

Thank you! Yeah I'm the same - if the first thing I see on a project page is some picture or video or output of what it's about I'm much more intrigued to read on.

[–] [email protected] 2 points 9 hours ago (2 children)

Tooting my own horn here and I know it's not a 1-1 replacement, but as others mentioned some great alternatives (diun, cup, wud) I'd like to suggest dockcheck.

 

Another few months have passed and thanks to a of user contributions and suggestions a bunch of changes got implemented, big and small.
The two latest changes have been pretty large:

  • Complete rewrite of notification logics
    • Configuration is set through the dockcheck.config
    • Templates used "untouched"
    • Possibility to trigger multiple notification templates through "channels"
  • Restructure the update process
    • First pulls all (selected) images
    • Then recreate all containers that received updates - to avoid unnecessary restarts and strain

https://github.com/mag37/dockcheck

Plenty more changes have been implemented since I posted last, such as:

  • Added a config-file to set user options (same as passing option flags).
  • Added option -u for unattended dockcheck self update (caution!).
  • Added option -I to print urls from url.list to list of containers with updates.
  • Cleaned up and refactored a lot of code;
    • Safer variables and pipefail options.
    • Consistent colorization of messages.
    • Monochrome mode hides progress bar.
    • Exits if pull or recreation of container fails.
  • Cleared up some readme with extra info;
    • Synology DSM
    • Prometheus + node_exporter
    • Zabbix config
    • Rest API script
    • Unraid wrapper script
  • Permission checks;
    • Graceful exit if no docker permissions.
    • pkg-manager installs handles sudo/doas/root properly.
  • Notify-templates; added slack, added markdown support to some templates.

I'm very happy to have a supportive and contributing user base who helps with troubleshooting, suggesting changes and contributing code. Thank you!

[–] [email protected] 1 points 2 months ago

Thank you for the update!

FYI: The first URL of the new page hits a 404 due to a faulty trailing space, the URL being hit is: https://news.elenarossini.com/%20

The correct url without trailing space:
https://news.elenarossini.com/

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

Thats really nice! Thank you so much for the writeup.

Would you mind if I added this as a discussion (crediting you and this post!) in the github project? Or if you'd like to copypaste it yourself to get the credit and be a part of the discussion.

[–] [email protected] 2 points 3 months ago

It's a different approach. This project started as a proof of concept - just to show that it's possible to check for updates without pulling the whole image first (which is how Watchtower does it).

Then it evolved to orchestrate granular automatic updates with a bunch of extra functionality - while still adhering to the core goal of keeping it simple and lightweight.

[–] [email protected] 2 points 3 months ago (5 children)

Thank you! Oh! That's pretty cool, do you mind sharing bits of how this is done? Would be nice to incorporate into a notify-template in the future.

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago) (1 children)

Thank you!

I sadly don't have too much insights in the other alternatives, I try to not compare too much - maybe I should study them a bit more to understand the wider picture. There's a few more I forgot to mention; renovate and dependabot.

While I think all those tools are great and have functionality that my project cant fulfill - I strive to keep dockcheck simple and lightweight. Options and functionality have been bolted on bit by bit while still trying to have it as simple as possible in its core functions - so a user could just download the main script dockcheck.sh and run it to list updates and optionally update. Everything else is optional, extras.

I guess it depends on what you're looking for. If you'd like a GUI or more in depth setup or reporting - I'd look elsewhere, but if you'd like simplicity and maybe schedule it to notify you when there's updates available - my project may be the thing.

So my answer would be yes: if you're running docker compose this project is very newbie friendly and easy to get going!

 

dockcheck is simple CLI tool to simplify keeping track of and updating your containers. Selective semi/fully auto updates, notifications on new versions and much more.

Another 6 months have passed and a bunch of updates have been made. The most recent ones are multi-threaded/asynchronous checks to greatly increase speed, notifications on new dockcheck release for those who run scheduled unattended checks, osx and bsd compatibility changes, prometheus exporter to push stats to eg. Grafana and more.

I'm happy to see the project still being used and improved by its users as I thought other great tools (dockge, wud, watchtower and others) would replace it.

As it's been a while I'll try to list the features:

  • Checks all your containers for new updates, without pulling.
  • Manually select which containers or choose all.
  • Either run it to auto update all, or not update any and just list results.
  • Tie it to notify you on new updates.
    • Templates: Synology DSM, mSMTP, Apprise, ntfy.sh , Gotify , Pushbullet , Telegram , Matrix, Pushover , Discord.
    • Enrich with urls to container release notes.
  • Optionally export metrics to Prometheus to show how many images got updates available in a graph.
  • Other misc options as:
    • Use labels to only update containers with label set.
    • Use a N days old option to only update images that have been stable release N days.
    • Auto prune dangling images.
    • Include stopped containers.
    • Exclude specific containers.

I've got to thank this community for contributing with donations, ideas, surfacing issues, testing and PRs. It's a joy!