Pi-Hole/docker-pi-hole
1
0
Fork 0
mirror of https://github.com/pi-hole/docker-pi-hole.git synced 2025-12-19 18:08:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revise Pi-hole Watchtower exclusion instructions

Browse Source 
Removed full explaination, reduced to a single link.

Signed-off-by: Alex Ferrarini <71784090+chippy01@users.noreply.github.com>
This commit is contained in:
Alex Ferrarini
2025-11-14 10:41:25 +01:00
committed by Adam Warner
parent f8d0e95070
commit 6afc54b5d0
1 changed files with 1 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@@ -300,19 +300,7 @@ 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.
If you wish to exclude the Pi-hole container from Watchtower's auto-update system take a look at [Full Exclude](https://containrrr.dev/watchtower/container-selection/#full_exclude) in Watchtower's docs.
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.