I’ve got around 10 services trying to start up, that all seem to be trying to use the same ip address. The start up logs look like this:
Choosing best nodes... Candidate node mine.node.dockerapp.io. State: Deployed. Total num containers: 284. Num containers from this service: 0 Choosing node mine.node.dockerapp.io because of the deployment strategy Scaling up... rge-1: Deploying in mine.node.dockerapp.io rge-1: Pulling image rocketchat/rocket.chat:latest in mine.node.dockerapp.io rge-1: Creating in mine.node.dockerapp.io with docker name rge-1.665a3bdd rge-1: Attaching container to overlay network dockercloud with ip 10.7.0.131 rge-1: Starting with docker id b13baacc738dee6959279f2238f0707aed79acbe392794254622b26448b2d34f in mine.node.dockerapp.io ERROR: rge-1: Address already in use ERROR: Service Scale action on 'rge' (using 'rocketchat/rocket.chat:latest') has failed
No matter how many times I try to redeploy it insists on using this ip for all of the hosts.
I’ve worked around this once when I had just a single container insisting on using this ip address, by redeploying the container (surprisingly it got a new ip) then manually going and removing the endpoint from the network. But now i’ve got 10 of them trying to use this same ip.
What’s weirder is its the same exact ip as I solved for before. Plenty of ip’s left in the /10 it has to provide addresses from… but for some reason its stuck on handing out this ip and this ip alone.