I am running TrueNAS Scale v25.04.1 and I am trying to install pi-hole to use as a local DNS alongside nginx-proxy-manager; however, when I try to install pi-hole via the Apps selection from TrueNAS or by a docker-compose.yaml file get an error stating that the port ‘53’ is in use.
So to verify I ran the following command: sudo lsof -i -P -n | grep LISTEN | grep :53 and sure enough the output stated dnsmasq 8880 nobody 9u IPv4 38385 0t0 TCP 10.189.97.1:53 (LISTEN)
I thought maybe It was due to possibly one of the Apps I already had running but none of them displayed using port 53, so to be a bit more thorough I started stopping most of the Apps running to see if anything would change, I did not shutdown all of them but the most used as well as the most likely apps, with no change. so Now I’m stuck wondering if this is just due to how TrueNAS Fangooth works? And if that is the case how can I install pi-hole so that I can use it alongside nginx-proxy-manager, for local SSL.
From what I can see, Incus is what powers the “Containers” functionality in TrueNAS? If I don’t use that (for now at least) can I disable it? In any case, the change you mentioned seems to have worked, pi-hole installed successfully.
I think this conflict should be documented, since the general use case for pi-hole would be for it to bind to port 53 and be used as DNS.
The conflict doesn’t really matter anymore since incus will be removed again next month. The experiment with it failed and the lxc functionality will be switched over to libvirt based lxcs. If that change will be nessessary for libvirt lxcs i do not know, i don’t have a spare system to update to the beta and play around with it.