All that's needed for execution is a Docker daemon that can pull from our registry. Currently there is a Docker-in-Docker daemon running in the runner pod, but really that could be something else. It could also be possible to choose one of multiple possible backends depending on RPZ metadata and user selection (both on the 'reproduce' page and via user accounts).
Example execution backends:
Another Docker server (give reproserver host + certificate, from docker-machine)
AWS (give reproserver IAM credentials and it'll start an EC2 instance to run your experiments on)
It could also be possible to run this without Docker. ReproUnzip supports Vagrant, and Vagrant supports AWS
Originally opened 2017-08-17 14:29 EDT by @remram44
All that's needed for execution is a Docker daemon that can pull from our registry. Currently there is a Docker-in-Docker daemon running in the runner pod, but really that could be something else. It could also be possible to choose one of multiple possible backends depending on RPZ metadata and user selection (both on the 'reproduce' page and via user accounts).
Example execution backends:
It could also be possible to run this without Docker. ReproUnzip supports Vagrant, and Vagrant supports AWS