So, just to follow up on this - we tried the installation of a new docker endpoint this week at the CHPC. The issue we came up against was the launching of the slave process on the containers remotely, let me elaborate.
The installation of the Docker endpoint and its configuration to allow remote API access was fine.
We could attach the endpoint as a docker cloud to the Jenkins server, and probe it.
Test jobs triggered on jenkins resulted in containers being launched on the remote endpoint
Test jobs could not launch the slave, and could not access the slave.
After some consideration, we determined that the problem was that the jenkins server at ci.sagrid.ac.za could not reach the slaves it launched over the network, since they were being instantiated on a private network address space on the remote site.
The only ways to solve this would be
- use a public address space
- assign each container a different port to be mapped to the ssh service running inside it from the public address
Neither of these is acceptable
Reminder : The fundamental issue is not being able to access the slave from the jenkins instance. We could solve this problem by having a new jenkins instance on the remote site and "federate" it somehow with the main one.
This is probably what we will do...