Access Containers by their IP's for Multi Tenant CaaS

Do you plan to support Container access directly via their IP address.

I tested another product called Solum attached it’s video where it deploys in Openstack , Are there plan for similar features ?


Hi Kanwar,

I’m not sure what you mean by being able to access containers directly via IP means. If you mean accessing the Docker bridge IP directly outside of the host, than, there is no way to access that except via publishing the ports of the application or creating your own bridge that is connected to some type of external switch that knows how to route to that IP.

If you mean accessing the container IP within the host or across hosts from another container, that is what Rancher’s managed networking does today by creating a network overlay across hosts using IPSec tunneling.

What specific features in Solum were you particularly looking for? Right now, it seems like Solum allows you to select GitHub URL, pull the project down, build it, and automatically launch it as a container in a host managed by Openstack. Rancher doesn’t do that out of the box but you can certainly integrate that with CI tools like Jenkins or Drone to do similar things (at least the pull + build outside of Rancher and then use Rancher to deploy the container in a set of hosts managed by Rancher.


Hi Will,

Thank you for the information, I appreciate the input,

You are right, I would like to access the Docker bridge IP’s from outside . Will try and see if I can setup a bridge on my end and route the IP’s

I find Solum’s version feature and ability to rollback as an very helpful option, Would be good to have this option in your product, Also would be good if I can download blueprint of a deployment in Rancher this would be similar to Heat Template/ Cloud Formation Template

Please let me know your thoughts


In our next release (v0.29.0), we will add the ability to do rolling upgrade as part of our RancherCLI. You can use this tool to upgrade from Service Av1 to Service Av2. Of course, if things fail, you can always rollback to Service Av1 from Service Av2 using the same option. All services that you create within a Stack are represented as a docker compose template so you can always download that template and use RancherCLI to create a new Stack with it if you wish to.