This message was deleted.
# rancher-desktop
a
This message was deleted.
r
This could be because traefik provided by Rancher Desktop uses the port 443. Can you please disable Traefik or Kubernetes and try again?
j
Hi @rapid-eye-50641, Thank you for your input. I haven't enabled Kubernetes, and this is the case with any port (not just 443).
Copy code
$ docker run -p 192.168.18.11:8080:80 nginx
docker: Error response from daemon: driver failed programming external connectivity on endpoint relaxed_dirac (072c107d06f4b73481d4fdb9a62b4220567aae9e4496c69702bb4aed8970f738): Error starting userland proxy: listen tcp4 192.168.18.11:8080: bind: cannot assign requested address.
ERRO[0000] error waiting for container:
r
What happens if you don't explicitly specify the ip address? Something like
docker run -p 8080:80 nginx
j
It works when I don't explicitly specific the IP address.
To give a bit more context, I am trying to help someone who is trying to run HashiCorp Nomad with Rancher Desktop, and the jobs fail, as Nomad tries to do this internally and fail.
This works with Docker Desktop.
https://asciinema.org/a/xzoXNmkKs6nPvVZrDDL4u6pX6 - An example that shows that it works on Docker Desktop. This is on the same machine.
r
Yeah, Rancher Desktop supports specifying 0.0.0.0 (all interfaces) or 127.0.0.1 for publishing a container port. If you specify 0.0.0.0 or don't specify the ip at all then you will be able to access the service via the primary interface too. If you still want the ability to explicitly bind to host address other than 0.0.0.0 or 127.0.0.1 for your use case, can you please file an enhancement request on the Rancher Desktop repo?