# dockcheck mit Homebrew installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für dockcheck in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:dockcheck ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install dockcheck ``` Evidenz: local Homebrew formula metadata ## Paketfakten - **Paketschlüssel:** brew:dockcheck - **Paketmanager:** Homebrew - **Version:** 0.8.2 - **Quellzusammenfassung:** CLI tool to automate docker image updates - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-07-28T03:32:18Z - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - dockcheck (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 0.8.2 ## Projektgeschichte und Nutzung Dockcheck is a Bash CLI for checking and optionally applying Docker image updates. Its README frames the tool around selective updates, include and exclude lists, image backups, labels, notifications, pruning, and Compose-aware container recreation. ### Projektgeschichte The maintainer's project writeup traces the idea to late 2022, when the original goal was to determine whether container images had updates without pulling every image first. The implementation settled on comparing local and remote image digests with help from regclient/regctl, turning a home-server maintenance annoyance into a reusable script. ### Adoptionsgeschichte Dockcheck's adoption is mostly self-hosting and homelab oriented: it is packaged for Homebrew in this batch, but the upstream README still documents direct script installation into a PATH directory and cron-style unattended checks. The README also points Podman users to the podcheck fork, which is a useful signal that its audience overlaps with container tinkerers who manage small fleets outside a full orchestration platform. ### Wie es verwendet wird Common usage is to scan running or stopped containers for newer images, choose which containers to update, pull the selected images, recreate containers or Compose stacks, and optionally prune dangling images afterward. Configuration lives in dockcheck.config beside the script or under ~/.config, and notifications are driven by shell templates plus channel-specific environment variables. ### Warum Paket-Nerds sich dafür interessieren Dockcheck is package-nerd interesting because it sits between heavy automated updaters and manual docker compose pull loops. It is a small shell tool built around registry digests, regctl, jq, and Compose conventions, so packaging it gives users a reproducible way to add conservative image-update checks to cron jobs and home servers. ### Zeitleiste - 2022: Maintainer describes the original idea forming around Christmas 2022. - 2024: Maintainer publishes a project history post explaining the digest-based approach. - 2026: The batch input lists Homebrew distribution for dockcheck. ### Related projects - Dockcheck is adjacent to Watchtower-style container updaters, Docker Compose maintenance scripts, regclient/regctl, and the podcheck fork for Podman users. ### Quellen - - - ## Sicherheitshinweise broad file, network, media, or database tool signal. - **Geiger-Risiko:** blue / mittel - broad file, network, media, or database tool signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ./dockcheck.config, ~/.config/dockcheck.config ## Combined YAML source View the package source record on GitHub. [combined/dockcheck.yml](https://github.com/mxcl/pkgdb/blob/main/combined/dockcheck.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph