From 0c35a906ce5c5a0657452c15a0a3f0e580249988 Mon Sep 17 00:00:00 2001 From: Matthew Jackson Date: Tue, 19 May 2026 08:03:46 -0700 Subject: [PATCH] watchtower: include + revive stopped containers MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit basement-ui's placeholder image exits immediately, so the container sits in a Restarting (0) loop. Watchtower's default filter only checks Up containers, so basement was being silently skipped every cycle — `scanned=1` in the running watchtower log was actually garage (pinned, no update available), not basement. INCLUDE_STOPPED=true makes watchtower check restart-looping / exited containers too. REVIVE_STOPPED=true starts them after the update so the new image actually runs. Once a working basement-ui image is pushed, this combo will pick it up and the container will stop restart-looping. --- unraid-1/watchtower.template.xml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/unraid-1/watchtower.template.xml b/unraid-1/watchtower.template.xml index 930eea1..9211fe1 100644 --- a/unraid-1/watchtower.template.xml +++ b/unraid-1/watchtower.template.xml @@ -51,4 +51,6 @@ Does not watch itself: a new Watchtower version requires re-Applying this templa 300 true true + true + true