spacelift.keyfile in a secure place. You’ll need it later, when launching workers in you worker pool.
spacelift.csrfile in the worker pool creation form. In response, you’ll receive a Spacelift token. It contains configuration for your worker pool launchers, as well as the certificate we generated for you based on the certificate signing request.
SPACELIFT_TOKEN- the token you’ve received from Spacelift on worker pool creation
SPACELIFT_POOL_PRIVATE_KEY- the contents of the private key file you generated, in base64.
SPACELIFT_DOCKER_CONFIG_DIR- if set, the value of this variable will point to the directory containing Docker configuration, which includes credentials for private Docker registries. Private workers can populate this directory for example by executing
docker loginbefore the launcher process is started;
SPACELIFT_MASK_ENVS- comma-delimited list of whitelisted environment variables that are passed to the workers but should never appear in the logs;
SPACELIFT_WORKER_NETWORK- network ID/name to connect the launched worker containers, defaults to
SPACELIFT_WORKER_EXTRA_MOUNTS- additional files or directories to be mounted to the launched worker docker containers, as a comma separated list of mounts in the form of
SPCELIFT_WORKER_RUNTIME- runtime to use for worker container;
SPACELIFT_WHITELIST_ENVS- comma-delimited list of environment variables to pass from the launcher's own environment to the workers' environment;
SPACELIFT_LAUNCHER_LOGS_TIMEOUT- custom timeout (the default is 7 minutes) for killing jobs not producing any logs. This is a duration flag, expecting a duration-formatted value, eg
SPACELIFT_LAUNCHER_RUN_INITIALIZATION_POLICY- file that contains the run initialization policy that will be parsed/used; If the run initialized policy can not be validated at the startup the worker pool will exit with an appropriate error;
SPACELIFT_LAUNCHER_RUN_TIMEOUT- custom maximum run time - the default is 70 minutes. This is a duration flag, expecting a duration-formatted value, eg.
SPACELIFT_METADATA_prefix will be passed on. As an example, if you're running Spacelift workers in EC2, you can do the following just before you execute the launcher binary: