Docker Based Runner for Behind-The-Firewall use
As a CircleCI SaaS user with Behind-the-firewall resources (artifacts, databases, services) I want to easily run select jobs on my internal network rather than CircleCI’s network.
Unlike current Machine Runner:
- I should not need to define or publish custom images I don’t or won’t use for my other jobs in cloud.
- I should not need to manage dependencies or libraries on said runner (instead provided by my docker images).
- I should not need to recycle physical or virtual servers to get a clean build environment (instead provided via each docker container – as with cloud).
In short, my existing cloud jobs should be easily ported to run on my docker runner in my internal network