From f8d0e95070d7f1c2885716e93f3affa6ba94982c Mon Sep 17 00:00:00 2001
From: Alex Ferrarini <71784090+chippy01@users.noreply.github.com>
Date: Wed, 12 Nov 2025 17:24:27 +0100
Subject: [PATCH] Add instructions for excluding Pi-hole from Watchtower
 updates

Added instructions to exclude Pi-hole container from Watchtower's  auto-update system.

Signed-off-by: Alex Ferrarini <71784090+chippy01@users.noreply.github.com>
---
 README.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/README.md b/README.md
index e715fdd..0138fff 100644
--- a/README.md
+++ b/README.md
@@ -300,6 +300,20 @@ We have noticed that a lot of people use Watchtower to keep their Pi-hole contai
   - If you care about your data (logs/customizations), make sure you have it volume-mapped or it will be deleted in this step.
 - Recreate the container using the new image.
 
+If you wish to exclude the Pi-hole container from Watchtower's auto-update system you can update the Docker-compose in the following way:
+```yml
+services:
+  pihole:
+    container_name: pihole
+    image: pihole/pihole:latest
+    #---------------------------------------------------
+    # Rest of the previous Docker-compose configuration
+    #---------------------------------------------------
+    labels:
+          - "com.centurylinklabs.watchtower.enable=false"
+```
+This will result in Watchtower avoiding the update check on this container leaving it as it is without any interaction.
+
 Pi-hole is an integral part of your network, don't let it fall over because of an unattended update in the middle of the night.
 
 # User Feedback