rancher-desktop Windows: timout error during pull dial tcp: lookup registry [...] i/o timeout

[regnalbokaj]

Actual Behavior

When pulling a larger (aka longer pull process) image from any registry (docker hub, microsoft artifact registry or private) the download hangs after some layers have been downloaded successfully. For Remaining layers which have not been pulled yet a "Retrying in ... second" countdown is shown, counts down from 15 seconds. When reached 1 second it again starts counting down from 15 seconds.
After a long time (multiple minutes) an error message is shown in terminal. From then all pulling (even smaller images like the "hello-world" example) aborts with the same error message.

Only a restart of rancher-desktop fixes this temporaly. But when pulling again, same error is shown.

Steps to Reproduce

Start rancher-desktop on Windows and pull an image.

Result

Error:
dial tcp: lookup registry-1.docker.io on 192.168.127.1:53: read udp 192.168.128.2:57251->192.168.127.1.53: i/o timeout

The shown IP-Adresses are from my home network. But actual I'm currently at my companies office. With another DNS Server. But doing a pull in my home network leads to the same error.

Expected Behavior

Pulling larger image should work without hanging during download.

Additional Information

I noticed this bug last week for the first time. Recentrly I updated rancher-desktop from 1.15.1 to 1.16. But i think image pulling still worked after the update (I do not perform pulls that often on my dev machine).
But I also tried to remove 1.16 and installed Version 1.15.1 again. But the result is the same as with Version 1.16.

I also tested Docker Desktop, which worked without this error.

Rancher Desktop Version

1.16

Rancher Desktop K8s Version

1.30.5 (deactivated)

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 11 Pro 10.0.22631 Build 22631

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

WatchGuard EPDR is running on my laptop.

[jandubois]

I have a suspicion that this is related to containers/gvisor-tap-vsock#393, which was only fixed last week. We have updated gvisor-tap-vsock in Rancher Desktop to 0.8.0, so you could give it a try if you are willing to run a CI build for testing. You may need to run a factory reset before/after switching between CI and release builds, so you will lose your existing setup. You can create a snapshot though before switching to the CI version, restore the snapshot after switching back.

[regnalbokaj]

I've tested it with Version 1.16.0-288-gc3853fcf0 from this build: https://github.com/rancher-sandbox/rancher-desktop/actions/runs/11557405306

But behaviour is still the same as described above.

I also noticed, that when building a container somtime it also cannot resolve the url of a package which should be installed defined in Dockerfile.