Container inaccessible over external IP on published port using docker

[bit-wrangler]

Actual Behavior

A connection cannot be established to the container app by hostname/IP address of the machine

Steps to Reproduce

1. Install Rancher Desktop
2. Configure it for dockerd and no kubernetes
3. Make sure port 8080 is allowed for connections in firewall
4. Run docker run -p 8080:80 -d dockerbogo/docker-nginx-hello-world
5. Get your IP address from ipconfig (or use your hostname)
6. Open browser and navigate to http://{your_ip_address or hostname}:8080 and the browser will fail to establish a connection

By comparison, if you navigate to http://localhost:8080, the page will load. Also, if Rancher Desktop is uninstalled and Docker Desktop is installed, same docker command is ran, and you navigate to http://{your_ip_address or hostname}:8080, the connection is established OK and page loads.

Result

A connection can't be established (in this example case, it's a connection refused error in browser)

Expected Behavior

When I run a docker container and publish its app's ports, I can connect to the app by using the host's hostname or IP address and the mapped port.

Additional Information

No response

Rancher Desktop Version

1.5.1

Rancher Desktop K8s Version

none

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 10 Enterprise 19044.1889

What CPU architecture are you using?

x64

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

No response

Windows User Only

SonicWall Global VPN Client (VPN connection not active during testing, local network IP address was used in tests). Carbon Black Cloud Sensor is present. Firewall rule was manually added to allow inbound connections to published port.

[adamkpickering]

Thanks for filing an issue! I just want to link this to #1180 and #1227 as it is related to those.