Offline Runner

Djinn CI can be used to run your builds offline without having to submit them to the build server. This does require having to configure the necessary drivers on your machine however.

Installing the Offline Runner

To install the offline runner you will first need to build it using Go,

$ git clone

once cloned, change into the directory and run the script.

$ ./ runner

This will produce a binary called bin/djinn, simply move this binary into a location that will make it accessible via your PATH.

Configuration Locations

For the offline runner, driver configuration sits in the driver.conf file. By default this is expected to be in the user config directory. Detailed below is where the file will be found on the different operating systems,


If non-empty then $XDG_CONFIG_HOME is used, and the fullpath would be $XDG_CONFIG_HOME/djinn/driver.conf. Otherwise it will use ~/.config/djinn/driver.conf.


On Darwin the path used will be, $HOME/Library/Application Support/djinn/driver.conf.


On Windows the path used will be, %AppData%/djinn.

Configuring Drivers

Note: The same driver configuration used for the offline runner is used for the worker too.

Each driver supported by Djinn CI is configured in its own block directive in the driver.conf file like so,

driver <name> {

where <name> is the name of the driver being configured, followed by a list of value directives. For example to configure the QEMU driver you would do the following,

driver qemu {
    disks  "/home/me/.config/djinn/images/qemu"
    cpus   1
    memory 2048

the above configuration would set the location of the QEMU disk images to use, the number of CPUs, and the amount of memory for each machine that will be created.

For a completed example of a driver.conf file see the dist directory of the source repository.


Detailed below are the value directives used by the Docker driver.

host string The host of the running Docker daemon, can be a path to a Unix socket.
version string The versio nof the Docker API to use.


Detailed below are the value directives used by the QEMU driver.

disks string Where the QEMU disk images are on the filesystem.
cpus int The number of CPUs to use for the QEMU machines.
memory int The amount of memory in bytes for the QEMU machines.

The directory specified in disks must have a another sub-directory for each architecture, in each of these exist the disk images to use. For example assume a manifest declares the following,

  type: qemu
  image: centos/8

then the offline runner will look for the following disk image,