adamant-kite-43734
10/24/2022, 7:52 PMwide-mechanic-33041
10/24/2022, 8:50 PMfast-garage-66093
10/24/2022, 8:53 PMhost.rancher-desktop.internal
is just another alias to access the host from inside the VM. It has the same value as host.docker.internal
. But yes, it should be in no_proxy
as well.wide-mechanic-33041
10/24/2022, 8:54 PMloud-megabyte-65691
11/16/2022, 2:37 PMhost.docker.internal
to resolve my host machine. I am on Windows 11 and Rancher-Desktop version 1.6.2
with dockerd
and Kubernetes version v1.24.4
😞
Do I need any additional configuration for that to work? I assumed that accessing my host via that address works out-of-the-boxfast-garage-66093
11/16/2022, 5:28 PMping
actually works, but can you connect via curl
? Are you using proxy settings? Could this be a VPN issue?loud-megabyte-65691
11/17/2022, 7:53 AMcurl
to host.docker.internal
I get the blue IIS page HTML back so that resolves and works, but when I try to connect to something running on a specific port, for instance my local Seq logging server which runs on port 5341, curl
to host.docker.internal:5341
does nothing. Same result for applications running on other ports. I don't use any proxy settings. Being on my company's VPN doesnt seem to make a difference.fast-garage-66093
11/17/2022, 5:12 PMcalm-sugar-3169
11/17/2022, 5:13 PMcalm-sugar-3169
11/17/2022, 6:00 PMping host.docker.internal
? does it just hang?loud-megabyte-65691
11/17/2022, 9:57 PMcalm-sugar-3169
11/17/2022, 9:59 PMNew-NetFirewallRule -DisplayName "WSL" -Direction Inbound -InterfaceAlias "vEthernet (WSL)" -Action Allow
and try pinging again?calm-sugar-3169
11/17/2022, 9:59 PMwsl
interface into the host networkloud-megabyte-65691
11/18/2022, 7:45 AMping
to host.docker.internal
and curl
to host.docker.internal:5341
are working.loud-megabyte-65691
11/18/2022, 7:47 AMcalm-sugar-3169
11/18/2022, 4:44 PMfast-garage-66093
11/18/2022, 5:42 PMfast-garage-66093
11/18/2022, 5:43 PMloud-megabyte-65691
11/21/2022, 7:23 AM