As @[email protected] already replied - some projects have many dependencies and images within their projects. And some have a bunch of containers and running a check with a tool that actually pulls all the images to do the check - those 100 pulls can be gone pretty quickly.
Oh thank you kindly! Haha, podcheck is a great fork if that fits your needs.
Thank you, forgot to add it! Glad it’s there.
Hey, thanks! It’s not the project logo though, just my usual user avatar. The project logo is prettier 😉
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.
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.
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.
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.
https://mag37.org/posts/linux_gaming/#battlenet-on-steamproton/
A bit old, but the section should be alright still.
Hey, I wrote a simple intro recently from guiding two friends into Fedora KDE without any previous knowledge. Its just an introduction really, but covers some basics.
https://mag37.org/posts/guide_newtolinux/
It does not cover dual booting though. As they both decided to fully swap after brief testing.
Others already mentioned Ventoy and that bricking isn’t really a risk - the worst you’d encounter is a complete wipe and restart so make sure you’ve got things backed up either way.
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.
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.
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/
Very nice! Now posted here: https://github.com/mag37/dockcheck/discussions/146
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.
deleted by creator
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.
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.
Thanks OP and others (especially @[email protected] ) for write-ups and insight!
I recently acquired a Kobo Elipsa 2E and started the journey experimenting. I’ve got a small library of mostly technical study books and ebooks/pdfs and some regular ebooks and comics that Id like to consume, in that order of importance. Set up Calibre-Web-Automated and Komga but not yet integrated with the Kobo in any way, but sure on the workflow.
But something that might be more important is a “read it later” setup of some sort. Currently experimenting with a self hosted Wallabag setup and KOReader. The sync is working fine, downloading the articles. Though I’d love to have a way of syncing highlights/annotations back somehow. And another thing is that images is not included in the KOReader side - so an article referencing a image of a chart for example will lack said image.
Anyone have any tips on their setup? Other alternatives or tweaks/options I might look into.