{"id":13552079,"url":"https://github.com/mag37/dockcheck","last_synced_at":"2025-10-21T04:50:07.625Z","repository":{"id":65532029,"uuid":"590406998","full_name":"mag37/dockcheck","owner":"mag37","description":"CLI tool to automate docker image updates. Selective, notifications, autoprune, no pre-pulling.","archived":false,"fork":false,"pushed_at":"2025-10-08T17:00:29.000Z","size":3515,"stargazers_count":1855,"open_issues_count":4,"forks_count":65,"subscribers_count":8,"default_branch":"main","last_synced_at":"2025-10-21T04:49:46.036Z","etag":null,"topics":["bash","docker","homelab","self-hosted"],"latest_commit_sha":null,"homepage":"https://mag37.org","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/mag37.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2023-01-18T10:47:49.000Z","updated_at":"2025-10-20T21:45:14.000Z","dependencies_parsed_at":"2023-11-19T20:26:10.547Z","dependency_job_id":"e857e36a-9cfd-4468-823e-2ed81b2496a9","html_url":"https://github.com/mag37/dockcheck","commit_stats":null,"previous_names":[],"tags_count":58,"template":false,"template_full_name":null,"purl":"pkg:github/mag37/dockcheck","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mag37%2Fdockcheck","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mag37%2Fdockcheck/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mag37%2Fdockcheck/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mag37%2Fdockcheck/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/mag37","download_url":"https://codeload.github.com/mag37/dockcheck/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mag37%2Fdockcheck/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":280207180,"owners_count":26290616,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-10-21T02:00:06.614Z","response_time":58,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["bash","docker","homelab","self-hosted"],"created_at":"2024-08-01T12:01:58.650Z","updated_at":"2025-10-21T04:50:07.619Z","avatar_url":"https://github.com/mag37.png","language":"Shell","readme":"\u003cp align=\"center\"\u003e\n  \u003cimg src=\"extras/dockcheck_colour.png\" width=\"300\" title=\"dockcheck\"\u003e\n\u003c/p\u003e\n\u003cp align=\"center\"\u003e\n  \u003cimg src=\"https://img.shields.io/badge/bash-4.3-green?style=flat-square\u0026logo=gnubash\" alt=\"bash\"\u003e\n  \u003ca href=\"https://www.gnu.org/licenses/gpl-3.0.html\"\u003e\u003cimg src=\"https://img.shields.io/badge/license-GPLv3-red?style=flat-square\" alt=\"GPLv3\"\u003e\u003c/a\u003e\n  \u003cimg src=\"https://img.shields.io/github/v/tag/mag37/dockcheck?style=flat-square\u0026label=release\" alt=\"release\"\u003e\n  \u003cbr\u003e\n  \u003ca href=\"https://ko-fi.com/mag37\"\u003e\u003cimg src=\"https://img.shields.io/badge/-Ko--fi-grey?style=flat-square\u0026logo=Ko-fi\" alt=\"Buy me a Coffee\"\u003e\u003c/a\u003e\n  \u003ca href=\"https://liberapay.com/user-bin-rob/donate\"\u003e\u003cimg src=\"https://img.shields.io/badge/-LiberaPay-grey?style=flat-square\u0026logo=liberapay\" alt=\"LiberaPay\"\u003e\u003c/a\u003e\n  \u003ca href=\"https://github.com/sponsors/mag37\"\u003e\u003cimg src=\"https://img.shields.io/badge/-Sponsor-grey?style=flat-square\u0026logo=github\" alt=\"Github Sponsor\"\u003e\u003c/a\u003e\n  \u003ca href=\"https://www.paypal.com/donate/?business=P2V5MCWRGCNBG\u0026no_recurring=0\u0026currency_code=SEK\"\u003e\u003cimg src=\"https://img.shields.io/badge/-PayPal-grey?style=flat-square\u0026logo=paypal\" alt=\"PayPal donation\"\u003e\u003c/a\u003e\n\u003c/p\u003e\n\n\u003ch2 align=\"center\"\u003eCLI tool to automate docker image updates or notifying when updates are available.\u003c/h2\u003e\n\u003ch3 align=\"center\"\u003eselective updates, exclude containers, custom labels, notification plugins, prune when done etc.\u003c/h3\u003e\n\n\u003ch4 align=\"center\"\u003e:whale: Docker Hub pull limit :chart_with_downwards_trend: not an issue for checks but for actual pulls - \u003ca href=\"#whale-docker-hub-pull-limit-chart_with_downwards_trend-not-an-issue-for-checks-but-for-actual-pulls\"\u003eread more\u003c/a\u003e\u003c/h4\u003e\n\n\u003ch5 align=\"center\"\u003eFor Podman - see the fork \u003ca href=\"https://github.com/sudo-kraken/podcheck\"\u003esudo-kraken/podcheck\u003c/a\u003e!\u003c/h4\u003e\n\n___\n## Changelog\n\n- **v0.7.3**: Bugfix - unquoted variable in printf list caused occasional issues. \n- **v0.7.2**:\n    - Label rework:\n      - Moved up label logic to work globally on the current run.\n      - Only iterating on labeled containers when used with `-l` option, not listing others.\n      - Clarified messaging and readme/help texts.\n    - List reformatting for \"available updates\" numbering to easier highlight and copy:\n      - Padded with zero, changed `)` to `-`, example: `02 - homer`\n      - Can be selected by writing `2,3,4` or `02,03,04`.\n- **v0.7.1**:\n    - Added support for multiple notifications using the same template\n    - Added support for notification output format\n    - Added support for file output\n    - Added optional configuration variables per channel to (replace `\u003cchannel\u003e` with any channel name):\n      - `\u003cchannel\u003e_TEMPLATE` : Specify a template\n      - `\u003cchannel\u003e_SKIPSNOOZE` : Skip snooze\n      - `\u003cchannel\u003e_CONTAINERSONLY` : Only notify for docker container related updates\n      - `\u003cchannel\u003e_ALLOWEMPTY` : Always send notifications, even when empty\n      - `\u003cchannel\u003e_OUTPUT` : Define output format\n- **v0.7.0**:\n    - Bugfix: snooze dockcheck.sh-self-notification and some config clarification.\n    - Added authentication support to Ntfy.sh.\n    - Added suport for sendmail in the SMTP-template.\n___\n\n\n![](extras/example.gif)\n\n## `dockcheck.sh`\n```\n$ ./dockcheck.sh -h\nSyntax:     dockcheck.sh [OPTION] [comma separated names to include]\nExample:    dockcheck.sh -y -x 10 -d 10 -e nextcloud,heimdall\n\nOptions:\n-a|y   Automatic updates, without interaction.\n-c D   Exports metrics as prom file for the prometheus node_exporter. Provide the collector textfile directory.\n-d N   Only update to new images that are N+ days old. Lists too recent with +prefix and age. 2xSlower.\n-e X   Exclude containers, separated by comma.\n-f     Force stop+start stack after update. Caution: restarts once for every updated container within stack.\n-F     Only compose up the specific container, not the whole compose stack (useful for master-compose structure).\n-h     Print this Help.\n-i     Inform - send a preconfigured notification.\n-I     Prints custom releasenote urls alongside each container with updates in CLI output (requires urls.list).\n-l     Only include containers with label set. See readme.\n-m     Monochrome mode, no printf colour codes and hides progress bar.\n-M     Prints custom releasenote urls as markdown (requires template support).\n-n     No updates, only checking availability.\n-p     Auto-Prune dangling images after update.\n-r     Allow checking for updates/updating images for docker run containers. Won't update the container.\n-s     Include stopped containers in the check. (Logic: docker ps -a).\n-t N   Set a timeout (in seconds) per container for registry checkups, 10 is default.\n-u     Allow automatic self updates - caution as this will pull new code and autorun it.\n-v     Prints current version.\n-x N   Set max asynchronous subprocesses, 1 default, 0 to disable, 32+ tested.\n```\n\n### Basic example:\n```\n$ ./dockcheck.sh\n. . .\nContainers on latest version:\nglances\nhomer\n\nContainers with updates available:\n1) adguardhome\n2) syncthing\n3) whoogle-search\n\nChoose what containers to update:\nEnter number(s) separated by comma, [a] for all - [q] to quit:\n```\nThen it proceeds to run `pull` and `up -d` on every container with updates.  \nAfter the updates are complete, you'll get prompted if you'd like to prune dangling images.\n\n___\n\n## Dependencies\n- Running docker (duh) and compose, either standalone or plugin. (see [Podman fork](https://github.com/sudo-kraken/podcheck)  \n- Bash shell or compatible shell of at least v4.3\n  - POSIX `xargs`, usually default but can be installed with the `findutils` package - to enable async.\n- [jq](https://github.com/jqlang/jq)\n  - User will be prompted to install with package manager or download static binary.\n- [regclient/regctl](https://github.com/regclient/regclient) (Licensed under [Apache-2.0 License](http://www.apache.org/licenses/LICENSE-2.0))  \n  - User will be prompted to download `regctl` if not in `PATH` or `PWD`.  \n  - regctl requires `amd64/arm64` - see [workaround](#roller_coaster-workaround-for-non-amd64--arm64) if other architecture is used.\n\n## Install Instructions\nDownload the script to a directory in **PATH**, I'd suggest using `~/.local/bin` as that's usually in **PATH**.  \nFor OSX/macOS preferably use `/usr/local/bin`.\n```sh\n# basic example with curl:\ncurl -L https://raw.githubusercontent.com/mag37/dockcheck/main/dockcheck.sh -o ~/.local/bin/dockcheck.sh\nchmod +x ~/.local/bin/dockcheck.sh\n\n# or oneliner with wget:\nwget -O ~/.local/bin/dockcheck.sh \"https://raw.githubusercontent.com/mag37/dockcheck/main/dockcheck.sh\" \u0026\u0026 chmod +x ~/.local/bin/dockcheck.sh\n\n# OSX or macOS version with curl:\n curl -L https://raw.githubusercontent.com/mag37/dockcheck/main/dockcheck.sh -o /usr/local/bin/dockcheck.sh \u0026\u0026 chmod +x /usr/local/bin/dockcheck.sh\n```\nThen call the script anywhere with just `dockcheck.sh`.\nAdd preferred `notify.sh`-template to the same directory - this will not be touched by the scripts self-update function.\n\n## Configuration\nTo modify settings and have them persist through updates - copy the `default.config` to `dockcheck.config` alongside the script or in `~/.config/`.  \nAlternatively create an alias where specific flags and values are set.  \nExample `alias dc=dockcheck.sh -p -x 10 -t 3`.\n\n## Notifications\nTriggered with the `-i` flag. Will send a list of containers with updates available and a notification when `dockcheck.sh` itself has an update.\n`notify_templates/notify_v2.sh` is the default notification wrapper, if `notify.sh` is present and configured, it will override.\n\nExample of a cron scheduled job running non-interactive at 10'oclock excluding 1 container and sending notifications:\n`0 10 * * * /home/user123/.local/bin/dockcheck.sh -nix 10 -e excluded_container1`\n\n#### Installation and configuration:\nSet up a directory structure as below.\nYou only need the `notify_templates/notify_v2.sh` file and any notification templates you wish to enable, but there is no harm in having all of them present.\n```\n .\n├── notify_templates/\n│   ├── notify_DSM.sh\n│   ├── notify_apprise.sh\n│   ├── notify_discord.sh\n│   ├── notify_generic.sh\n│   ├── notify_gotify.sh\n│   ├── notify_HA.sh\n│   ├── notify_matrix.sh\n│   ├── notify_ntfy.sh\n│   ├── notify_pushbullet.sh\n│   ├── notify_pushover.sh\n│   ├── notify_slack.sh\n│   ├── notify_smtp.sh\n│   ├── notify_telegram.sh\n│   └── notify_v2.sh\n├── dockcheck.config\n├── dockcheck.sh\n└── urls.list         # optional\n```\n- Uncomment and set the `NOTIFY_CHANNELS=\"\"` environment variable in `dockcheck.config` to a space separated string of your desired notification channels to enable.\n- Uncomment and set the environment variables related to the enabled notification channels. Eg. `GOTIFY_DOMAIN=\"\"` + `GOTIFY_TOKEN=\"\"`.\n\nIt's recommended to only do configuration with variables within `dockcheck.config` and not modify `notify_templates/notify_X.sh` directly. If you wish to customize the notify templates yourself, you may copy them to your project root directory alongside the main `dockcheck.sh` (where they're also ignored by git).  \nCustomizing `notify_v2.sh` is handled the same as customizing the templates, but it must be renamed to `notify.sh` within the `dockcheck.sh` root directory.  \n\n\n#### Snooze feature:\nConfigure to receive scheduled notifications only if they're new since the last notification - within a set time frame.\n\n**Example:** *Dockcheck is scheduled to run every hour. You will receive an update notification within an hour of availability.*  \n**Snooze enabled:** You will not receive a repeated notification about an already notified update within the snooze duration.  \n**Snooze disabled:** You will receive additional (possibly repeated) notifications every hour.  \n\nTo enable snooze uncomment the `SNOOZE_SECONDS` variable in your `dockcheck.config` and set it to the number of seconds you wish to prevent duplicate alerts.  \nSnooze is split into three categories; container updates, `dockcheck.sh` self updates and notification template updates.\n\nIf an update becomes available for an item that is not snoozed, notifications will be sent and include all available updates for that item's category, even snoozed items.\n\nThe actual snooze duration will be 60 seconds less than `SNOOZE_SECONDS` to account for minor scheduling or run time issues.\n\n\n#### Current notify templates:\n- Synology [DSM](https://www.synology.com/en-global/dsm)\n- Email with [mSMTP](https://wiki.debian.org/msmtp) (or deprecated alternative [sSMTP](https://wiki.debian.org/sSMTP))\n- Apprise (with it's [multitude](https://github.com/caronc/apprise#supported-notifications) of notifications)\n  - both native [caronc/apprise](https://github.com/caronc/apprise) and the standalone [linuxserver/docker-apprise-api](https://github.com/linuxserver/docker-apprise-api)\n  - Read the [QuickStart](extras/apprise_quickstart.md)\n- [ntfy](https://ntfy.sh/) - HTTP-based pub-sub notifications.\n- [Gotify](https://gotify.net/) - a simple server for sending and receiving messages.\n- [Home Assistant](https://www.home-assistant.io/integrations/notify/) - Connection to the notify [integrations](https://www.home-assistant.io/integrations/#notifications).\n- [Pushbullet](https://www.pushbullet.com/) - connecting different devices with cross-platform features.\n- [Telegram](https://telegram.org/) - Telegram chat API.\n- [Matrix-Synapse](https://github.com/element-hq/synapse) - [Matrix](https://matrix.org/), open, secure, decentralised communication.\n- [Pushover](https://pushover.net/) - Simple Notifications (to your phone, wearables, desktops)\n- [Discord](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks) - Discord webhooks.\n- [Slack](https://api.slack.com/tutorials/tracks/posting-messages-with-curl) - Slack curl api\n\nFurther additions are welcome - suggestions or PRs!\n\u003csub\u003e\u003csup\u003eInitiated and first contributed by [yoyoma2](https://github.com/yoyoma2).\u003c/sup\u003e\u003c/sub\u003e\n\n#### Notification channel configuration:\nAll required environment variables for each notification channel are provided in the default.config file as comments and must be uncommented and modified for your requirements.  \nFor advanced users, additional functionality is available via custom configurations and environment variables.  \nUse cases - all configured in `dockcheck.config`:  \n(replace `\u003cchannel\u003e` with the upper case name of the of the channel as listed in `NOTIFY_CHANNELS` variable, eg `TELEGRAM_SKIPSNOOZE`)\n- To bypass the snooze feature, even when enabled, add the variable `\u003cchannel\u003e_SKIPSNOOZE` and set it to `true`.\n- To configure the channel to only send container update notifications, add the variable `\u003cchannel\u003e_CONTAINERSONLY` and set it to `true`.\n- To send notifications even when there are no updates available, add the variable `\u003cchannel\u003e_ALLOWEMPTY`  and set it to `true`.\n- To use another notification output format, add the variable `\u003cchannel\u003e_OUTPUT` and set it to `csv`, `json`, or `text`. If unset or set to an invalid value, defaults to `text`.\n- To send multiple notifications using the same notification template:\n  - Strings in the `NOTIFY_CHANNELS` list are now treated as unique names and do not necessarily refer to the notification template that will be called, though they do by default.\n  - Add another notification channel to `NOTIFY_CHANNELS` in `dockcheck.config`. The name can contain upper and lower case letters, numbers and underscores, but can't start with a number.\n  - Add the variable `\u003cchannel\u003e_TEMPLATE` to `dockcheck.config` where `\u003cchannel\u003e` is the name of the channel added above and set the value to an available notification template script (`slack`, `apprise`, `gotify`, etc.)\n  - Add all other environment variables required for the chosen template to function with `\u003cchannel\u003e` in upper case as the prefix rather than the template name.\n    - For example, if `\u003cchannel\u003e` is `mynotification` and the template configured is `slack`, you would need to set `MYNOTIFICATION_CHANNEL_ID` and `MYNOTIFICATION_ACCESS_TOKEN`.\n\n### Release notes addon\nThere's a function to use a lookup-file to add release note URL's to the notification message.  \nCopy the notify_templates/`urls.list` file to the script directory, it will be used automatically if it's there.  \nModify it as necessary, the names of interest in the left column needs to match your container names.  \nTo also list the URL's in the CLI output (choose containers list) use the `-I` option or variable config.  \nFor Markdown formatting also add the `-M` option. (**this requires the template to be compatible - see gotify for example**)  \n\nThe output of the notification will look something like this:\n```\nContainers on hostname with updates available:\napprise-api  -\u003e  https://github.com/linuxserver/docker-apprise-api/releases\nhomer  -\u003e  https://github.com/bastienwirtz/homer/releases\nnginx  -\u003e  https://github.com/docker-library/official-images/blob/master/library/nginx\n...\n```\nThe `urls.list` file is just an example and I'd gladly see that people contribute back when they add their preferred URLs to their lists.\n\n## Asyncronous update checks with **xargs**; `-x N` option. (default=1)\nPass `-x N` where N is number of subprocesses allowed, experiment in your environment to find a suitable max!  \nChange the default value by editing the `MaxAsync=N` variable in `dockcheck.sh`. To disable the subprocess function set `MaxAsync=0`.\n\n\n## Extra plugins and tools:\n\n### Using dockcheck.sh with the Synology DSM\nIf you run your container through the *Container Manager GUI* - only notifications are supported.  \nWhile if running manual (vanilla docker compose CLI) will allow you to use the update function too.  \nSome extra setup to tie together with Synology DSM - check out the [addons/DSM/README.md](./addons/DSM/README.md).\n\n### Prometheus and node_exporter\nDockcheck can be used together with [Prometheus](https://github.com/prometheus/prometheus) and [node_exporter](https://github.com/prometheus/node_exporter) to export metrics via the file collector, scheduled with cron or likely.\nThis is done with the `-c` option, like this:\n```\ndockcheck.sh -c /path/to/exporter/directory\n```\n\nSee the [README.md](./addons/prometheus/README.md) for more detailed information on how to set it up!  \n\u003csub\u003e\u003csup\u003eContributed by [tdralle](https://github.com/tdralle).\u003c/sup\u003e\u003c/sub\u003e  \n\n### Zabbix config to monitor docker image updates\nIf you already use Zabbix - this config will show numbers of available docker image updates on host.  \nExample: *2 Docker Image updates on host-xyz*  \nSee project: [thetorminal/zabbix-docker-image-updates](https://github.com/thetorminal/zabbix-docker-image-updates)\n\n### Serve REST API to list all available updates\nA custom python script to serve a REST API to get pulled into other monitoring tools like [homepage](https://github.com/gethomepage/homepage).  \nSee [discussion here](https://github.com/mag37/dockcheck/discussions/146).\n\n### Wrapper Script for Unraid's User Scripts\nA custom bash wrapper script to allow the usage of dockcheck as a Unraid User Script plugin.  \nSee [discussion here](https://github.com/mag37/dockcheck/discussions/145).\n\n## Labels\nOptionally add labels to compose-files. Currently these are the usable labels:\n```\n    labels:\n      mag37.dockcheck.update: true\n      mag37.dockcheck.only-specific-container: true\n      mag37.dockcheck.restart-stack: true\n```\n- `mag37.dockcheck.update: true` will when used with the `-l` option only check and update containers with this label set and skip the rest.  \n- `mag37.dockcheck.only-specific-container: true` works instead of the `-F` option, specifying the updated container when doing compose up, like `docker compose up -d homer`.\n- `mag37.dockcheck.restart-stack: true` works instead of the `-f` option, forcing stop+restart on the whole compose-stack (Caution: Will restart on every updated container within stack).\n\nAdding or modifying labels in compose-files requires a restart of the container to take effect.\n\n## Workaround for non **amd64** / **arm64**\n`regctl` provides binaries for amd64/arm64, to use on other architecture you could try this workaround.\nRun regctl in a container wrapped in a shell script. Copied from [regclient/docs/install.md](https://github.com/regclient/regclient/blob/main/docs/install.md):\n\n```sh\ncat \u003eregctl \u003c\u003cEOF\n#!/bin/sh\nopts=\"\"\ncase \"\\$*\" in\n  \"registry login\"*) opts=\"-t\";;\nesac\ndocker container run \\$opts -i --rm --net host \\\\\n  -u \"\\$(id -u):\\$(id -g)\" -e HOME -v \\$HOME:\\$HOME \\\\\n  -v /etc/docker/certs.d:/etc/docker/certs.d:ro \\\\\n  ghcr.io/regclient/regctl:latest \"\\$@\"\nEOF\nchmod 755 regctl\n```\nTest it with `./regctl --help` and then either add the file to the same path as *dockcheck.sh* or in your path (eg. `~/.local/bin/regctl`).\n\n## Docker Hub pull limit :chart_with_downwards_trend: not an issue for checks but for actual pulls\nDue to recent changes in [Docker Hub usage and limits](https://docs.docker.com/docker-hub/usage/)\n\u003eUnauthenticated users: 10 pulls/hour  \n\u003eAuthenticated users with a free account: 100 pulls/hour\n\nThis is not an issue for registry checks. But if you have a large stack and pull more than 10 updates at once consider updating more often or to create a free account.\nYou could use/modify the login-wrapper function in the example below to automate the login prior to running `dockcheck.sh`.\n\n### Function to auth with docker hub before running\n**Example** - Change names, paths, and remove cat+password flag if you rather get prompted:\n```sh\nfunction dchk {\n  cat ~/pwd.txt | docker login --username YourUser --password-stdin\n  ~/dockcheck.sh \"$@\"\n}\n```\n\n## `-r flag` disclaimer and warning\n**Wont auto-update the containers, only their images. (compose is recommended)**  \n`docker run` dont support using new images just by restarting a container.  \nContainers need to be manually stopped, removed and created again to run on the new image.  \nUsing the `-r` option together with eg. `-i` and `-n` to just check for updates and send notifications and not update is safe though!\n\n## Known issues\n- No detailed error feedback (just skip + list what's skipped).\n- Not respecting `--profile` options when re-creating the container.\n- Not working well with containers created by **Portainer**.\n- **Watchtower** might cause issues due to retagging images when checking for updates (and thereby pulling new images).\n\n## Debugging\nIf you hit issues, you could check the output of the `extras/errorCheck.sh` script for clues.\nAnother option is to run the main script with debugging in a subshell `bash -x dockcheck.sh` - if there's a particular container/image that's causing issues you can filter for just that through `bash -x dockcheck.sh nginx`.\n\n## License\ndockcheck is created and released under the [GNU GPL v3.0](https://www.gnu.org/licenses/gpl-3.0-standalone.html) license.\n\n## Sponsorlist\n\n:small_orange_diamond: [avegy](https://github.com/avegy)\n:small_orange_diamond: [eichhorn](https://github.com/eichhorn)\n:small_orange_diamond: [stepdg](https://github.com/stepdg)\n:small_orange_diamond: [acer2220](https://github.com/acer2220)\n:small_orange_diamond: [shgew](https://github.com/shgew)\n:small_orange_diamond: [jonas3456](https://github.com/jonas3456)\n:small_orange_diamond: [4ndreasH](https://github.com/4ndreasH)\n:small_orange_diamond:\n\n___\n\n### The [story](https://mag37.org/posts/project_dockcheck/) behind it. 1 year in retrospect.\n","funding_links":["https://ko-fi.com/mag37","https://liberapay.com/user-bin-rob/donate","https://github.com/sponsors/mag37","https://www.paypal.com/donate/?business=P2V5MCWRGCNBG\u0026no_recurring=0\u0026currency_code=SEK"],"categories":["Shell","bash","Development with Docker","self-hosted"],"sub_categories":["CI/CD"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmag37%2Fdockcheck","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmag37%2Fdockcheck","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmag37%2Fdockcheck/lists"}