Hi,
Thanks for your response!
So as of now, I am only only mentioning the private port (the exposed port of the container.)
My tomcat instance is running on 8080 within the container so I add “8080” in the ‘private port’ and leave the public port blank so that it’s allocated dynamically. I also scale it to a certain number before I spin off the service. But after the first container, it returns a port conflict error.
In my docker-compose.yml file, I mention ports in the following manner:
** ports:**
** :“8080”**
When I spin it up using docker-compose and scale it to a certain number, there is no port conflict. When I do it on Rancher, it returns a port conflict error.
Maybe I am missing some step.
Thank you. 