Nice!

I’ve never really ran any of the immutable/atomic distros for daily driver so can’t give you tips from experience. But this seemed sensible (but a bit in depth, maybe just take parts of it). https://lurkerlabs.com/fedora-silverblue-ultimate-post-install-guide/

And if you’re looking at atomic/immutable, also check out Bluefin, Aurora and Bazzite (based on Fedora).

• https://projectbluefin.io/
• https://getaurora.dev/en
• https://bazzite.gg/

Good luck!

Glad the boot option worked, hope it’ll work out with the drivers installed.

And if you have not yet installed RPM-fusion and Nvidia drivers properly - you could take a look at the Graphics section on this writeup: https://github.com/wz790/Fedora-Noble-Setup

Can you edit the kernel parameters in Grub (by pressing E on the Fedora alternative) and try adding nomodeset or nvidia_drm.modeset=0 at the end of the line starting with linux /boot/vmlinuz or similar. Then CTRL+X to start with the new (temporary) parameters.

If that boots (and if you’ve installed the Nvidia drivers etc) - try forcing a rebuild of kmods and wait 5-10 minutes before restarting.
sudo akmods --force --rebuild
You can see if it’s don’t by running sudo journalctl -f -u akmods

Maybe you have to remove the kmod prior, can’t recall:
dnf remove kmod-nvidia-$(uname -r)

So true 😂 Both at work and private side projects 👏

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.

Sadly no, only within the scope of the tag specified in the compose.

Renovate, WUD or Diun might be other options for that!

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.