@benzman81 I managed to reproduce this in the version you mentioned, however, I also tested this in our previous versions 1.11.1 (of course not using Network Tunnel), and it still did not work. It looks as though we have never supported the host network driver mode. However, after reading the documents closely, if you use -p to publish your ports, you will probably achieve what you are trying to do on Rancher Desktop. Once you use the published port flag, you can use one of the following domains to access your port on the host from the container.

host.docker.internal

or

host.rancher-desktop.internal

Can I ask you what is your use case? so, I can help you better.

@Nino-K hi, we use vscode with RancherDesktop, WSL and Devcontainer. Until 1.15.x all ports from WSL have been available in the devcontainer and all servers started in devcontainer were available outside the devcontainer in WSL( my collegues are using 1.13.x to 1.14.x I think, some may use older versions but without devcontainer). Since ports on both side are not fixed as it differs per developer and use case, we used host network for starting the devcontainer. Now v1.15. stops us from upgrading. Hope that helps.

I think I understand a bit better, can you guys avoid using --net=host argument and use -p (published ports) instead?

As I stated, since ports are not fixed I do not know how to solve this. It is not defined which server and how many a developer starts in wsl oder in the devcontainer.

We are experiencing the same issue. I am working with an older Rancher Desktop version (1.10.0) and the network mode "host" seems to work fine. A colleague, who's working with Rancher Desktop 1.15.1, is not able to see anything published with network mode "host". While port mapping is still an option, the network mode "host" helps with reducing clutter in our docker-compose file, so it would be nice to be able to use it