Configuration

Custom Runner

A runner is the "backend" of Dagger where containers are actually executed.

Custom Registry Mirrors

Dagger can be configured to use container registry mirrors for any registry URL. This allows container images that refer to one registry to instead be redirected to a different one.

Custom Certificate Authorities

Dagger can be configured to use custom certificate authorities (CAs) when communicating with external services like container registries, Git repositories, etc.

Service Proxies

Dagger can be configured to use HTTP(S) proxies to connect to external HTTP services. This configuration applies to "core" operations like pulling container images, cloning Git repositories, etc. and is also supplied to user containers in the form of standard environment variables.

Dagger Cloud

Dagger Cloud requires a GitHub account for identity verification. If you don't have one, register for a free GitHub account before proceeding.

Modules

Modules can be configured by editing their dagger.json file. The configuration in there contains all module metadata - from the name of the module and the SDK it uses, to the dependencies it requires. An initial configuration is automatically generated when using dagger init or dagger develop for the first time, and is kept up-to-date with dagger config/dagger install/etc.

Cache

Dagger caches two types of data: