From b2d80d036a1896b6d278d40c0ea89874142c9c44 Mon Sep 17 00:00:00 2001 From: mag37 Date: Wed, 14 May 2025 20:55:09 +0200 Subject: [PATCH] info about -r option --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index dab4307..4e33e3d 100644 --- a/README.md +++ b/README.md @@ -250,17 +250,18 @@ function dchk { } ``` +## :warning: `-r flag` disclaimer and warning +**Wont auto-update the containers, only their images. (compose is recommended)** +`docker run` dont support using new images just by restarting a container. +Containers need to be manually stopped, removed and created again to run on the new image. +Using the `-r` option together with eg. `-i` and `-n` to just check for updates and send notifications and not update is safe though! + ## :hammer: Known issues - No detailed error feedback (just skip + list what's skipped). - Not respecting `--profile` options when re-creating the container. - Not working well with containers created by **Portainer**. - **Watchtower** might cause issues due to retagging images when checking for updates (and thereby pulling new images). -## :warning: `-r flag` disclaimer and warning -**Wont auto-update the containers, only their images. (compose is recommended)** -`docker run` dont support using new images just by restarting a container. -Containers need to be manually stopped, removed and created again to run on the new image. - ## :wrench: Debugging If you hit issues, you could check the output of the `extras/errorCheck.sh` script for clues. Another 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`.