Since its initial release, Rancher has included cross-host networking for containers. For storage, we introduced the Convoy storage driver framework, which enabled Docker containers to access persistent storage volumes implemented by NFS or EBS.
Now, in Rancher 1.2 we're introducing fully pluggable networking and storage frameworks for Rancher environments. In our September 2016 Online meetup we introduced this concept and demonstrated how to deploy new Rancher storage services.
During Jenkins Build- make run-Jenkins 1m 10
This could be any CI, so longs as it can be run in a container and everyone can build in a consistent way then it doesn’t matter what its doing.
As part of this build it could be executing unit tests etc
I’ve mapped through the drive but you could just as easily have it git pull into the container, my instance monitors the remote git repo and then builds it from the mapped drive. There are pros and cons to both, I like this as I can make changes and run a manual build without needing to check in all the time.
Jenkins git build – 5 mins
Running multiple hosts locally causes pain as it means you need a repository or a means to get the built containers between the hosts. Overlay network also doesn’t currently work in boot2docker