Introduction

TD-StorageBay provides shared and private runners for continuous integration and continuous deployment of projects. The main shared runner can handle 20 jobs at a time. This means that of everyone attempting to use the runner, it will process up to 20 jobs in parallel. If you feel that you need a dedicated runner for your project or group, contact support (customer-support@mail.tdstoragebay.com) and submit your request. A dedicated runner will only handle 10 jobs at once, but only your project(s) or group(s) will be allowed to submit jobs to it.

The runners

Each runner is a Docker powered runner service on a dedicated VM. Currently, the runners are allowed to pull Docker images from any source, by specifying an image key in the CI file.

Custom hosts

Due to the network setup at TD-StorageBay, every server has to have a custom /etc/hosts to make sure it can access the others. The same applies to docker containers. Instead of a custom hosts file being installed from the Dockerfile, however, the runner is configured with the extra_hosts directive so that all containers and images can access the public-facing parts of TD-StorageBay. NOTE: All private / back-end servers are not listed in the extra hosts for Docker containers.

DinD runner

If, for some reason, you need to run a Docker container within the runner, there are two steps to make this possible:

1. Tag the job (using tags) with "dind".
2. Specify the docker:dind service with services.

With this done, the Docker in Docker requiring job will be run on the DinD runner.