• 2 Posts
  • 21 Comments
Joined 2 years ago
cake
Cake day: December 29th, 2023

help-circle



  • 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)








  • 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.