Open ryanelian opened 4 years ago
I am hitting this same issue with WSL 2. For me it is Cisco Umbrella Client, which must be using dnscrypt-proxy under the covers. This only happens to me if I try to use it with both WSL 2 and Hyper-V at the same time. I got it working with WSL 2 alone, and then it broke again when I put Hyper-V back on.
PS> Get-Process -Id (Get-NetUDPEndpoint -LocalPort 53).OwningProcess
Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
116 11 1412 6660 20364 0 dnscrypt-proxy
209 15 11000 18640 4432 0 svchost
I have the same issue. I want to add that changing dnscrypt-proxy service to listen on 127.0.1.1:53 doesn't avoid the issue. It needs to be disabled completely followed by a reboot to allow WSL to work.
Related issue: https://github.com/microsoft/WSL/issues/4364
Docker using WSL2 backend crashes upon startup when DNSCrypt Windows Service created by SimpleDnsCrypt is running.
This probably has something to do with port 53 being used by DNSCrypt