I have an app that I’ve deployed using the rancher-compose CLI and the stack is defined in a docker-compose.yml and rancher-compos.yml. I even have automated upgrades of this app plugged in to our Jenkins pipeline…so it works well using rancher-compose and the Rancher API. This stack runs 2 services and 2 load balancers on 2 VM hosts, so pretty standard, and simple stuff.
So I thought I’d add a catalog entry for this stack…just for fun.
The problem I’m seeing is that the load balancers don’t come up properly. The first to come up seems to listen on a random port, and the other never comes up…I assume because it can’t communicate with first one.
My original docker-compose.yml had the ports: set to - 6666, and it worked. When changed it to - “6666:6666” the first load balancer to come up listened on port 6666 properly, but the second one still won’t come up. It’s not trying to run on the same host, so there is not a port conflict. And there are no logs from the failing load balancer, because it’s not getting that far.
What am I missing? What can I look at to get a clue?