This message was deleted.
# rancher-desktop
a
This message was deleted.
w
yeah i don't think that
host
will work for WSL2 since the network namespace is in the VM so the host can't see it. best would be standard port mappings. gut says any of the WSL based tools would have the same issue. maybe with windows containers it might work, but the isolation model is quite different compared to linux
f
what is interesting, for testing purposes, I've installed Ubuntu in WSL, there I've installed docker engine and run the same containers, with same settings (they are even located on Windows hard drive, I've accessed them through
/mnt/c/...
and
network_mode: host
works just fine - I can access these containers on Windows - so it is definitely possible
w
yup could be how networking is handled in the distro because of k3s, but also the hosttunneling feature to assist with VPNs
you may want to see if the internal bridge ip allows for host https://github.com/rancher-sandbox/rancher-desktop/issues/6515
f
I know @calm-sugar-3169 has just been working on some networking fixes related to host mode (not sure if that is finished yet), so it is possible that this will work in 1.17 (when it is released).