Last updated on 27 February 2025
Bridge Mode
Drop the compose below into your Project YAML section, if you are also setting up Unbound copy the additional YAML below the Pi-hole compose
YAML
services:
pihole:
image: pihole/pihole:latest
container_name: pihole-bridge
cap_add:
- CAP_NET_RAW
- CAP_NET_BIND_SERVICE
- CAP_CHOWN
# - CAP_NET_ADMIN #uncomment if you want to use DHCP
- CAP_SYS_NICE
- CAP_SYS_TIME
environment:
- PIHOLE_UID=1234 #CHANGE_TO_YOUR_UID
- PIHOLE_GID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- FTLCONF_webserver_api_password=YOURPASSWORD
- FTLCONF_dns_listeningMode=all
- DNSMASQ_USER=pihole
volumes:
- /volume1/docker/pihole:/etc/pihole
ports:
- 53:53/udp
- 8000:80/tcp
- 8443:443/tcp
labels:
- com.centurylinklabs.watchtower.enable=false
restart: unless-stopped
# if using unbound paste it hereYAML
unbound:
image: klutchell/unbound
container_name: unbound
ports:
- 5335:53/tcp
- 5335:53/udp
volumes:
- /volume1/docker/unbound:/etc/unbound/custom.conf.d
restart: unless-stoppedWe are now changing some settings to the YAML based on your User IDs and Timezone etc
| Section | Explanation |
|---|---|
| PIHOLE_UID= | This UID is the one you obtained when setting up your dockerlimited user in the earlier guide at the start of the page. This tells Pi-hole to run under this user rather than root and gives it access to the folders we created. |
| PIHOLE_GID= | As per the above this line will be the GID you obtained earlier. |
| TZ= | You will need to change this line to your own timezone code – you can find the correct list of ones to use on wikipedia.org/wiki/List_of_tz_database_time_zones |
| FTLCONF_webserver_ api_password= | Change this to the password you would like to use for the Web UI |
You can now jump ahead to Page 5 for the final configuration.
I’ve used plenty of your guides and today I’ve encountered my first problem — I made my changes to the pihole YAML code, pasted it in and all looked fine, but when I paste the YAML for the unbound portion of the project I get the error “Property unbound is not allowed” and can not progress any further this is on a Synology DS1819+ running DSM 7.2.2.-72806 update 3.
Given the updated guide was just posted today I’m hoping there might be a minor syntax/formatting issue that I’m just not seeing. Any help you can offer will be appreciated.
Hey – I have double tested the compose, and they seem to paste in OK for me, can you reply with your compose.
https://paste.drfrankenstein.co.uk
It will give you a URL to use.
Amazing job, I finally managed to put a pihole on my Synology. Now, quick question. Few days after 6.0 upgrade and reinstall everything from scratch, they updated again to some 6.0.3 build. Following your guide, I used the docker update feature, it worked fine and pihole is working properly, but now I have two containers:
pihole-pihole-1 pihole/pihole:latest greyed out
pihole-macvlan pihole/pihole:latest green
Question is, am I supposed to delete the first one?
Hey – So the update should have removed the first install. You can safely delete it.