-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network routing problem to intranet servers on VPN #2505
Comments
@rcsilva83 can you please try enabling experimental host resolver and let us know if it fixes the issue. Thanks |
@Nino-K it didn't work. |
seems similar issue #2477 |
Yes, @ripun . Indeed it seems to be a similar issue with different VPN software. |
I hope issue gets resolved sooner , because this is kind of blocker for windows user with VPN to access private docker registries (docker pull/push/login are must) |
@rcsilva83 a few questions:
Thanks, |
Yes, I did
Microsoft Always On VPN |
Just a hint: Podman with |
@rcsilva83 please use our latest release 1.9 which includes a solution for when using Rancher Desktop behind a VPN. You can enable it using:
I'm going to close this issue, feel free to re-open it if the issue still persists. |
Actual Behavior
After starting Rancher Desktop, my WSL distros get
Destination Host Unreachable
error when pinging to intranet servers. As a result, I also can't use my corporate Docker registry with Rancher Desktop.Steps to Reproduce
wsl --shutdown
to ensure a clean environmentping corporate.docker.repo
with success:ping corporate.docker.repo
inside Ubuntu WSL distribution with error.Result
Expected Behavior
Additional Information
No response
Rancher Desktop Version
1.4.1
Rancher Desktop K8s Version
Disabled
Which container runtime are you using?
moby (docker cli)
What operating system are you using?
Windows
Operating System / Build Version
Windows 10 Enterprise 21H2
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
No response
Windows User Only
Microsoft Always On VPN.
The text was updated successfully, but these errors were encountered: