jombi

Hi folks, Sorry to hijack this thread, but I've just started having this same issue with my PiHole container. Initially it was working for a few days, and then after performing unraid OS upgrade from 6.11.4 to 6.11.5 the container wouldn't start (though the version change is likely unrelated and it could have been triggered by the reboot, but more info = more better). Using command netstat -tunlp | grep ":53" I can see that the port is in use by dnsmasq, so the error itself is obviously correct. I can see dnsmasq is listening on the same "strange IP address" referred to previously, but that just appears to be the virtual interface virbr0 address. Using command netstat -tunlp | grep "dnsmasq" it looks like the only ports this process is listening for are the ones relating to the pihole container (TCP 53, UDP 53, and UDP 67) To my knowledge (unless there's a setting I haven't noticed), I don't have anything configured on the system that should be doing DNS/DHCP aside from the PiHole container. Which then leaves me with a series of questions: Is it most likely that the dnsmasq service running and listening to these ports as a result of the creation of the container, or is it always running and listening on these ports on account of the fact that it is by it's nature a DNS/DHCP service? It seems this service is running at bootup and listening on these ports. Is it possible/safe to either stop it from listening on these ports or stop it from running at bootup, or is it required for the container to work or even just something else in the system? Are there any system logs somewhere that might indicate when this service was first started? I can only assume it was after my creation of the container, as I was obviously able to create and run it in the first place. I'm by no means knowledgeable in Linux/unraid/Docker, so at this point I'm still trying to figure out what role dnsmasq plays in the system and I'm hoping people can forgive my ignorance if my questions/assumptions are way off the mark. Any direction I can get would be greatly appreciated as I'm probably heading down the completely wrong path here. Thanks for your time if you made it this far EDIT: After some further reading, I found that disabling VMs on the VM Manager page stops dnsmasq and allows the pihole container to run as normal. I think this might be related to a VM that I ran temporarily? After setting up PiHole I booted up pfSense in a VM but didn't really go anywhere with it and removed it after about 30 minutes, but it seems this is a lingering artifact of that setup. In any case, it doesn't seem the issue is related to "Docker Engine", but I at least have some direction to investigate how to un-do whatever the VM did - leaving this here in the hopes this info helps someone else!