Failing on ports, but port is available

Archive Rancher 1.x
1

We’re seeing the message 500 Server Error: Internal Server Error ("Cannot start container 0ca5aea79da4005bf97ba8e583626677b6fd14c1859ce2429f284aa33aced16b: failed to create endpoint <load-balancer-name> on network bridge: Bind for 0.0.0.0:10400 failed: port is already allocated")
however, port 10400 is not in use, confirmed both by Rancher and by running netstat on the host directly.

Where can we look next for why this load balancer won’t schedule?

2

if you run docker ps -a on the host is anything mapped to port 10400?

1 Like
3

You nailed it. Somehow, I don’t see that container in Rancher, or that port in netstat, but it’s there…