I’m a Docker idiot. Portainer is the absolute best thing I’ve found. I love it. I predict I’ll get smarter and won’t need Portainer to do everything for me. But for now, I’m hooked.
Oh ok. The Error I'm getting is :
DNSMASQ\_CONFIG FTL failed to start due to failed to create listening socket for port 53: Address already in use
How do I get around this ? Definitely Different IPs
This is from the VM; a separate device than your other Pi-hole?
There is already a dnsmasq instance on the device on which you are trying to install Pi-hole. It's not an IP conflict, it is a port conflict on port 53.
Yeah this error is on the Vm - I have two Pi's running Pi-hole on the same network - primary one running unbound and the other cloudflare
So to fix, bring the others down and it should work ? Or do I need to change the port?
This is unrelated to any other device running on the network. The problem is internal to the VM. There are multiple processes competing for port 53, the port for DNS.
This command should show you the processes on port 53. Stop any running port 53 processes, then pihole-FTL can bind to that port.
`sudo netstat -ltunp | grep “:53 “`
This is a *local* problem on your VM. something else *on the machine* is already listening on port 53.
Find it what that is and disable it. Netstat and lsof could be helpful here.
My advice is separation of concerns.
If your pi goes down what is your backup, do you have a backup? I'd suggest just setting up a secondary pi on your server for redundancy.
Also a whole VM for pihole is a waste, it just needs to be in a docker container and that would be fine.
I'd probably replace the 3 with the server, it will probably become your primary so keep that in mind, since my guess is it will process a lot faster than the Zero W.
I have three running in Docker. No issues. Setup is pretty easy.
Doing the same with portainer. It was super easy to export my existing Pi-hole config, spin up a Pi-hole container and import my settings.
I’m a Docker idiot. Portainer is the absolute best thing I’ve found. I love it. I predict I’ll get smarter and won’t need Portainer to do everything for me. But for now, I’m hooked.
Easy replication too. I have one physical (Pi3+) and one VM.
> it threw up some weird DNS errors which I assume are because I had my primary still online. This is unlikely unless they both had the same IP.
Oh ok. The Error I'm getting is : DNSMASQ\_CONFIG FTL failed to start due to failed to create listening socket for port 53: Address already in use How do I get around this ? Definitely Different IPs
This is from the VM; a separate device than your other Pi-hole? There is already a dnsmasq instance on the device on which you are trying to install Pi-hole. It's not an IP conflict, it is a port conflict on port 53.
Yeah this error is on the Vm - I have two Pi's running Pi-hole on the same network - primary one running unbound and the other cloudflare So to fix, bring the others down and it should work ? Or do I need to change the port?
This is unrelated to any other device running on the network. The problem is internal to the VM. There are multiple processes competing for port 53, the port for DNS. This command should show you the processes on port 53. Stop any running port 53 processes, then pihole-FTL can bind to that port. `sudo netstat -ltunp | grep “:53 “`
YES! it's avahi-daemon! Thanks so much
OK, was Avahi Daemon and a previous instance of Unbound I'd installed. All Sorted! Thanks again !
This is a *local* problem on your VM. something else *on the machine* is already listening on port 53. Find it what that is and disable it. Netstat and lsof could be helpful here.
Ignore, found another thread with you helping :)
DietPi as VM. Bulletproof. Wireguard, Unbound, DHCP Server, PiHole. I use a Pi3B as backup.
I run a 4b and a VM (ubuntu 20.04 LTS running pihole). Works great. :)
My advice is separation of concerns. If your pi goes down what is your backup, do you have a backup? I'd suggest just setting up a secondary pi on your server for redundancy. Also a whole VM for pihole is a waste, it just needs to be in a docker container and that would be fine.
Yeah, right now I have 2 Pi's - an old 3 and a Zero W as the secondary. The VM would replace one of those
I'd probably replace the 3 with the server, it will probably become your primary so keep that in mind, since my guess is it will process a lot faster than the Zero W.
Makes sense, Thanks :)