GitHub - mag37/dockcheck: CLI tool to automate docker image updates. Interactive or unattended with notifications, image backups, autoprune, no pre-pulling and more.
github.com
CLI tool to automate docker image updates. Interactive or unattended with notifications, image backups, autoprune, no pre-pulling and more. - mag37/dockcheck

Dockheck is a CLI tool to automate docker image updates. Interactively or unattended with notifications, image backups, exclude/include, labels, autoprune and more. Can be run as is, without configuration or with extensive options.

This year my AFK-life have been intense, so development have been slow and mainly squashing bugs. But others have kept contributed with suggestions on improvements, ideas on new features and some ready to merge patches.
So these last couple of weeks I’ve tried to squeeze in some time to bring it together in v0.8.0 and now v0.8.1.

New stuff in short:

Docker Compose -ready:

  • Now possible to run dockcheck within its own docker compose container (or docker run).
  • Easily set up your notifications and options, either in conf-file or env-vars, then let it run as any other container.
  • Optionally run it once interactively with docker run, no need for configs.
  • Run interactively between your scheduled compose setup with docker exec -it as usual.

New options:

  • -N No updates or checks; simulating updates to test notifications unconditionally.
  • -E Exclude containers from applying updates but check available, separated by comma.
  • -C Temporarily use default configs - override dockcheck.config file.
  • -o Hides the “No updates available” message and only shows updateable images.

New notification templates:

  • Home Assistant Event Integration
  • XMPP
  • Bark

I’m very happy this project still got traction considering all the large alternatives around. Wonderful community!

Disclaimer: No AI tools used what so ever from my end and encouraging contributors to refrain and/or explain.

[CBH]

  • irmadlad@lemmy.worldEnglish
    1·
    14 hours ago

    That looks pretty cool.

    Docker Hub pull limit 📉 not an issue for checks only for actual pulls

    Has anyone actually ran into this road block? The limit is something like 100 pulls per 6 hours for unauthorized pulls. Just curious. I have some 53 containers running, but I couldn’t imagine running 100 of them. I guess there are some who do.

    • mag37@lemmy.mlOPEnglish
      2·
      6 hours ago

      As @epyon22@sh.itjust.works 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.

        • epyon22@sh.itjust.worksEnglish
          2·
          14 hours ago

          Usually if I’m updating everything prior to having more automated updates. Some projects like next cloud and and matrix have deep dependency trees