The log file directory must be created before you start the service: $ mkdir /var/log/drone-runner-exec If the user is non-root: DRONE_LOG_FILE=.drone-runner-exec/log.txt If the user is root: DRONE_LOG_FILE=/var/log/drone-runner-exec/log.txt The file location is determined by the user running the process. The log file location should be configured in the environment file before you start the service. The exec runner writes logs to a file on the host machine. This must match the secret defined in your Drone server configuration. DRONE_RPC_SECRET provides the shared secret used to authenticate with your Drone server. DRONE_RPC_PROTO provides the protocol used to connect to your Drone server. The runner connects to the server at the host address to receive pipelines for execution. DRONE_RPC_HOST provides the hostname (and optional port) of your Drone server. See Configuration for a complete list of configuration options. This article references the below configuration options. Bash syntax and Bash expressions are not supported. This file should use the syntax =value which sets the variable to the given value and # for comments.

If the user is not-root: ~/.drone-runner-exec/config If the user is root: /etc/drone-runner-exec/config The environment file location is determined by the user running the process. The exec runner is configured using an environment variable file. $ sudo install -t /usr/local/bin drone-runner-execĭownload for i386 architectures: $ curl -L | tar zxĭownload for 32-bit arm: $ curl -L | tar zxĭownload for 64-bit arm: $ curl -L | tar zx You will need to modify the below commands to use the latest release.ĭownload for amd64 architectures: $ curl -L | tar zx The exec runner is packaged in binary format and distributed as a Github release. This article explains how to install the exec runner on Linux.

Download marathoner