Docker UDP Port 53 conflicts with VM Service

[veritas2884]

I run ADGuard and use my unRAID box as a dns for my router. When I spin up the VM service I have to kill ADGuard or I get a "Libvirt Service failed to start." How do I make it so I can run the VM service not have it use port 53?

[veritas2884]

Figured it out. I set the docker image to the Br:0 network setting and assigned it a random fixed IP address. I then pointed my router's DNS to that IP. Rebooted and I now have VM, ad-blocking, and no conflicts. 

[karloldreyes]

On 7/13/2021 at 12:40 PM, veritas2884 said:

I run ADGuard and use my unRAID box as a dns for my router. When I spin up the VM service I have to kill ADGuard or I get a "Libvirt Service failed to start." How do I make it so I can run the VM service not have it use port 53?

Hey reviving this old thread. Why does having adguard on port 53 cause that error? I'm getting that error pretty regularly and trying to figure out if its one of my docker containers.

[ilarion]

53 is the port for dns... if it is shared between unraid and adguard one of them will not have dns i suppose  that is why it has to put it on external network bridge not on internal docker one.So that you can assign it ip of the unraid network not of the docker one.