logs.zip
I have attached logs here

wsl.log contains a lot of loops of:

2024-12-20T12:10:56.541Z: Capturing output: wsl.exe --distribution rancher-desktop --exec cat /proc/net/route
2024-12-20T12:10:56.892Z: captureCommand:
command: (cat '/proc/net/route')
output: <Iface  Destination     Gateway         Flags   RefCnt  Use     Metric  Mask            MTU     Window  IRTT                                                       
eth3    00000000        0101A8C0        0003    0       0       25      00000000        0       0       0                                                                              
docker0 000011AC        00000000        0001    0       0       0       0000FFFF        0       0       0                                                                            
eth3    0001A8C0        00000000        0001    0       0       281     00FFFFFF        0       0       0                                                                             
eth3    0101A8C0        00000000        0005    0       0       25      FFFFFFFF        0       0       0                                                                              
veth-rd-wsl     008FA8C0        00000000        0001    0       0       0       00FFFFFF        0       0       0                                                                        
>

That means it's stuck because the code is failing around

So the issue seems to be that we're unexpectedly not seeing eth0 (but there's eth3 instead). We may need to fall back to any interface that has a destination of all zeros, but I'd be curious to know about why the interface name is different.

(Having a different distribution with a local dockerd should be no issue; I have that too, just with openSUSE. Also, thanks for uploading the logs!)

Thanks for clarifying. I don't know the exact mapping for the network interfaces in WSL. Are they directly referring to the actual network interfaces on the host system, or is there some internal mapping in the WSL layer to avoid issues with this?

I am using a dock, so my PC has two ethernet ports, the native "Ethernet" is not in use, while the one on the dock "Ethernet 2" is. If this is also mapped into WSL, perhaps this answers the question. I can try to plug the network cable directly into my laptop to see if this resolves the issue for now.

No immediate difference in the behaviour, still seems to be looping. However it seems that it now continues from the check mentioned before but is still looping back, perhaps due to a failure in the next steps?

I have uploaded new logs below.
logs.zip

The WSL networks should be unrelated to your host networks. There's #6665 (which should hopefully be fixed in 1.17), but I'm not sure that's related to this issue.

Looks like your new logs are a lot more complex, which does make me wonder if you have networkingmode=mirrored set. Can you check if that's the case?

You are exactly right. I have had to setup mirrored networking mode in the past to get wsl to work properly with the proxy/vpn setup that I use in my work. I did not realize that this would have an effect on new distributions as well. But I would believe that rancher would experience similar networking issues in my daily setup where I would need to access company repositories, etc.

Would this still be resolved by supporting other network adapter names. Or is mirrored networking mode not supported on purpose?