Skip to content

Commit 4cd166c

Browse files
authored
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>
1 parent 7c2dff0 commit 4cd166c

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

README.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -300,6 +300,20 @@ We have noticed that a lot of people use Watchtower to keep their Pi-hole contai
300300
- If you care about your data (logs/customizations), make sure you have it volume-mapped or it will be deleted in this step.
301301
- Recreate the container using the new image.
302302
303+
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:
304+
```yml
305+
services:
306+
pihole:
307+
container_name: pihole
308+
image: pihole/pihole:latest
309+
#---------------------------------------------------
310+
# Rest of the previous Docker-compose configuration
311+
#---------------------------------------------------
312+
labels:
313+
- "com.centurylinklabs.watchtower.enable=false"
314+
```
315+
This will result in Watchtower avoiding the update check on this container leaving it as it is without any interaction.
316+
303317
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.
304318

305319
# User Feedback

0 commit comments

Comments
 (0)