From d6b908a5923b03c15a9d14eec60ee360f3e0f63d Mon Sep 17 00:00:00 2001 From: Lionel Sambuc Date: Tue, 6 Jan 2026 10:57:33 +0100 Subject: [PATCH] chore: Upgraded to v6 --- docker-compose.yml | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index 39fcfbb..a4ee41a 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -7,7 +7,7 @@ networks: # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ services: pihole: - image: pihole/pihole:2024.07.0 + image: pihole/pihole:2025.11.1 ports: # LSC: I am not relying on Traefik to proxy DNS, in order to not loose # name resolution when restarting the reverse proxy. @@ -19,19 +19,29 @@ services: # Web UI handled through Traefik #- "9000:80/tcp" environment: + # Set the appropriate timezone for your location from + # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones, e.g: TZ: "Europe/Zurich" + FTLCONF_misc_etc_dnsmasq_d: 'true' + # If using Docker's default `bridge` network setting the dns listening mode should be set to 'ALL' + FTLCONF_dns_listeningMode: 'ALL' WEBPASSWORD_FILE: "/webpassword" # Volumes store your data between container upgrades volumes: - "./conf/webpassword:/webpassword:ro" + # For persisting Pi-hole's databases and common configuration file - "./etc-pihole/:/etc/pihole/:rw" - - "./etc-dnsmasq.d/:/etc/dnsmasq.d/:rw" + # Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards. Needs environment variable FTLCONF_misc_etc_dnsmasq_d: 'true' + #- "./etc-dnsmasq.d/:/etc/dnsmasq.d/:rw" - "./etc-pihole-updatelists:/etc/pihole-updatelists/:rw" - # Recommended but not required (DHCP needs NET_ADMIN) - # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities - # LSC: Commented out, DHCP already handeld #cap_add: + # # See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities + # # Required if you are using Pi-hole as your DHCP server, else not needed # - NET_ADMIN + # # Required if you are using Pi-hole as your NTP client to be able to set the host's system time + # - SYS_TIME + # # Optional, if Pi-hole should get some more processing time + # - SYS_NICE restart: always networks: - proxy_infra