To customize the runner deployment instructions (which shouldn't be required for most use cases), add flags to the automatically generated deployment configuration file or change the default values.
Retrieve the content of the automatically generated file. For example, for the following install command
curl -H "Content-Type: application/x-sh" -s -L "https://link.torq.io/***z5v5qBRg21otM8" | sh, run: curl -H "Content-Type: application/x-sh" -s -L "https://link.torq.io/***z5v5qBRg21otM8"
Copy the command output and paste it into a fresh line.
Add flags or change values according to your needs. These are two examples:
Specify a proxy server:
-e https_proxy=http://XXXXXXX:PORT
. Make sure you replace
XXXXXXX:PORTwith your actual proxy address and port.Connect to a bridge network:
-e DOCKER_NETWORK_ID='XXXXXXXXXXX' -e DOCKER_NETWORK_NAME='XXXXXXXXXX'. A bridge network uses a software bridge that allows containers connected to the same bridge network to communicate while providing isolation from containers that are not connected to that bridge network.
Run the edited deployment configuration file.
Run
docker psto confirm that the service is running.To retrieve the edited deployment configuration file at any time, use the command:
docker inspect --format "$(curl -Ls https://link.torq.io/7Yoh)" $(docker ps | grep spd | awk '{print $1}')The retrieved configuration file can be used to deploy the runner on a new machine.