I have deployed rancher 1.2 recently and noticed a lot of changes from the previous version. Could someone help me to address the following queries?
- If an application is deployed via rancher 1.2, its port mapping details are not showing while using docker cli(docker ps). Docker inspect doesnt have that information and have to go to rancher to find out the host port where its mapped. Is it normal behavior?.. is there anyway to find out this info from the docker cli?
- Also docker private network(172.17 range) IP also not getting assigned to containers while deploying through rancher catalogs, though linking is done using the rancher private IPs. However, is it possible to assign those docker private IPs too? Atleast, can we see the rancher IPs using any docker or other commands from the commandline, instead of getting into the container?
- Many stacks are auto deployed while creating the rancher server, thereby creating atleast 7 containers in each hosts which appears to unpleasent when we look into (docker ps)… Are all these containers required for the proper networking? how to change the behavior of the stack by redeploying, like creating a different subnet? Can we just delete the stack and then bring it as a private catalog for deploying it newly? How will it affect the current networking?
- Containers deploying through rancher catalog has the name “r-stackname-servicename-randomcharacters”. I had tried to override it using container_name in the docker-compose.yml, but it failed too. Do we have anyother possibilities to create the container with a different name?