Docker Raito CLI Runner

Raito Docker Registery

All Raito Docker images are registered at our Github packages. You can find images for linux/386, linux/amd64 and linux/arm64 architectures.

You can easily pull the latest image by executing:

$> docker pull ghcr.io/raito-io/raito-cli-runner:latest

Start Docker Raito CLI Runner

To run the Raito CLI run command continuously, a docker container can be used.

The image expects a Raito configuration file mounted to /config/raito.yml. Read more about the Raito CLI configuration here.

You can easily start the container using the following command:

$> docker run --mount type=bind,source="<Your local Raito configuration file>",target="/config/raito.yml",readonly ghcr.io/raito-io/raito-cli-runner:latest

The default entrypoint of the container is defined as

ENTRYPOINT /raito-cli-runner run -f $CLI_FREQUENCY --config-file /config/raito.yml --log-output

You can override the default entrypoint by using the --entrypoint option when execution docker run

Logs

By default, the log output of the Raito CLI are forwarded to /dev/stdout and /dev/stderr. If you like to forward to a specific (mounted) file, override the default locations by configuring RAITO_CLI_CONTAINER_STDOUT_FILE and RAITO_CLI_CONTAINER_STDERR_FILE environment variables.

$> docker run --mount type=bind,source="<Your local Raito configuration file>",target="/config/raito.yml",readonly -v <Directory to store logs>:/logs/ --env "RAITO_CLI_CONTAINER_STDOUT_FILE=/logs/output.txt" --env "RAITO_CLI_CONTAINER_STDERR_FILE=/logs/err.txt" raito-cli-runner:latest

Environment variables

The following environment variables are used in the default entrypoint:

Additional environment variables, that could be referred in your Raito configuration file, can be mounted by using the existing docker environment arguments --env and --env-file.