Last updated on 27 February 2025
Important or Recent Updates
| Historic Updates | Date |
|---|---|
| Updated guide for Container Manager and using Macvlan | 14/05/2023 |
| Added a new section to ensure DSM continues having network access. | 02/06/2023 |
| Guide updated so you can choose between Macvlan or Bridge mode | 12/08/2023 |
| Added additional security option to the compose to restrict the container from gaining new privileges | 25/10/2023 |
| Fixed issues I introduced with the recent changes in my mission to make things more secure. It was so secure I broke it! Added the appropriate permissions/capabilities at start up for the container. | 29/10/2023 |
| Removed the requirement for the synobridge as this container can just use its own bridge, and added the Host network mode, so all three are a choice. | 28/01/2024 |
| Removed the WEB_UID and WEB_GID from the config to avoid issues with ID’s conflicting inside the container. I will update again once I have some time to work around this. | 03/04/2024 |
| Some minor amends to sync up the information across this guide and the AdGuard one | 01/08/2024 |
| Removed two unneeded capabilities from the bridge version of the docker compose as they are not required. | 16/11/2024 |
| Guide updated for the all new v6 of Pi-hole (Note if you upgrade from v5 you effectively have to change all the compose settings in line with the new guide so might be worth just scrapping and starting fresh unless you really need stats etc Please note as recommended by the Pi-hole dev team I have added a Watchtower exclusion label to the compose so you can do manual updates. Automated ones could result in you losing internet access if a bad update takes place. Edited again today as I left in a variable that is not required in Host and Macvlan mode “DNSMASQ_LISTENING” sorry. | 20/02/2025 |
| Had a rethink of the Guide, and it has been rewritten to include an overdue request of including Unbound! | 24/02/2025 |
What is Pi-hole?
If you are looking to get advertising and tracking blocked across all the devices on your network a Pi-hole will have you covered. It’s a locally hosted Domain Name Server and uses block lists to stop adverts.
This guide will get you set up with Pi-hole and cover some basic initial settings, I recommend checking out the documentation for all the various features available.
What is Unbound (Optional)
Unbound is a validating, recursive, caching DNS resolver. Rather than using an upstream DNS provider such as Google or Cloudflare who will look up the IP addresses for domain names you visit Unbound does this for you. It queries root servers for the address for a website. For example when you visited this site its actually on the server 213.186.33.50. This adds a layer of privacy in your web browsing as you are not relying on a third party with this information.
Host vs Bridge vs Macvlan Network Modes
You need to decide which mode of Networking you want to use, I have outlined the key points below in general order of preference. (Unbound will be on a bridge which has no impact on your choice)
Host:
Host mode uses your NAS underlying network to run the containers network services, so it will be reliant on the NAS not using any of the required ports for the container. However, this makes it easy to set up, but you need to make sure no other service is using the required ports. All your clients will appear correctly as independent devices and stats.
Bridge Mode:
The main benefit of Bridge Mode will be the ease of setup however you will find that all clients on your network will appear under the same IP as the Bridge 172.20.0.1. This won’t impact ad blocking, but it will mean you can apply device specific rules etc.
Macvlan:
This gives you the benefit of Pi-hole having its own IP address on your network, all clients appear with their real IP addresses allowing you to assign specific rules and give you some nicer stats. However, one downside is that your NAS will not be able to use Pi-hole for DNS, due to the additional security features of Macvlan and its communication with its host. This is generally not an issue unless you wanted to use your Ad blocking with Tailscale.
Please note you will not be able to use Macvlan with a Bonded network connection e.g. ‘Bond0’. You will need to remove the bond in order to use this method.
Let’s Begin
In order for you to successfully use this guide you will need to check that your Router allows you to change your network DNS servers, this is usually found in the DHCP settings.
Please follow the initial guide below to get a restricted Docker user set up, then come back here.
Folder Setup
Let’s start by getting some folders set up for the container to use. Open up File Station create the following.
/docker/projects/pihole-compose
/docker/pihole
/docker/unbound #Optional
Unbound Configuration (Optional)
We need to make a config file for Unbound to define its network settings.
Download the file below and put it into the “unbound” folder we created earlier
Container Manager
Next we are going to set up a ‘Project’ in Container Manager. Open up Container Manager and click on Project then on the right-hand side click ‘Create’.
In the next screen we will set up our General Settings, enter the following:
| Section | Setting |
|---|---|
| Project Name: | pihole |
| Path: | /docker/projects/pihole-compose |
| Source: | Create docker-compose.yml |
The code section of the below will be blank until we move to the next step.
Next we are going to drop in our docker compose configuration. You now need to decide if you are going to go with Host, Bridge Mode or Macvlan. Jump to the appropriate page to follow the setup.
Host – Page 2
Bridge – Page 3
Macvlan – Page 4
Is it possible to do a docker compose that features a MACVLAN that also utilises unbound too?
I’ve been able to use cbcrowe/pihole-unbound:latest, but it doesn’t utilise a MACVLAN so the client list isn’t populated, it just shows one source. 172.21.0.1
Hey, I would have to try it out as not been using Unbound for a couple of years. Once I do some testing certainly an option to add that in.
Which ip address am I adding to my router’s DNS settings to point it to the pi-hole? The same as the IP I use to access the web ui? 192.168.xx.xx? Or the 9.9.9.9 and 1.1.1.1?
Fixed the final paragraph to make it clearer on what to use.
Hello! Amazing resource as always, thanks so much. I’ve setup my macvlan network as described (my router is 192.168.1.1):
config:
– subnet: “192.168.1.0/24”
ip_range: “192.168.1.254/24”
gateway: “192.168.1.1”
However when I build I get the error “failed to create network macvlan: Error response from daemon: failed to allocate gateway (192.168.1.1): Address already in use”.
Any ideas what could be causing this?
Do you already have a MACVLAN set up within Container Manager > Networks as this can clash. You will need to remove it if so and then define any containers you want on a MACVLAN within this same project.
Goodday,
Thank you for your clear tutorials they have helped me resolve some errors in the passed.
I have no IT background whatsoever. I just like trying new things with my Synology NAS.
Recently I started using Container Manager. However with Pi-hole I run into an error which I dont understand:
Error,2023/11/07 01:08:08,Iwan,Start container pihole failed: {“message”:”driver failed programming external connectivity on endpoint pihole (7c99c89137c466356bb4ceedd5030e……………………): Error starting userland proxy: listen tcp4 0.0.0.0:8000: bind: address already in use”}.
It looks like to me like a conflict with a previous installation, where i did manage to open Pi-hole but than the DNS was not working/starting.
Is there anyway to solve this?
Thank you!
Hey, thanks for the feedback. I would double check you have completely removed the other container and also make sure you don’t have anything else on port 8000. Sometimes a reboot can clear things up if a port has not been released. Doesn’t happen often but worth a shot.
In the query log I only see address 172.20.0.1, is it possible to see the ip addresses of the clients that do the lookup?
You would need to run the container in MACVLAN mode in order for it to act independently of the Docker Bridge which is handling the routing.