Pi-hole Port 53 Conflict

When deploying Pi-hole on Docker using Deployrr, you might encounter an error indicating that port 53 is already in use. This typically occurs because systemd-resolved is listening on port 53, which Pi-hole needs for DNS services.

Error Message

You might see an error similar to this when trying to deploy Pi-hole:

Error response from daemon: driver failed programming external connectivity on endpoint pihole: failed to bind host port for 0.0.0.0:53:172.18.0.18:53/tcp: address already in use

Solution

To resolve this issue, follow these steps:

Edit the systemd-resolved configuration file:
```
sudo nano /etc/systemd/resolved.conf
```
Add or modify the following line in the configuration:
```
DNSStubListener=no
```
Restart the systemd-resolved service:
```
sudo systemctl restart systemd-resolved
```
"Full" delete PiHole using Deployrr Stack Manager
Redeploy Pi-hole through Deployrr

After following these steps, Pi-hole should deploy successfully with port 53 available for use.

Sources

Discord Thread: @https://discord.com/channels/974306760171073556/1346884572138438667/1347161142794911825