Skip to main content

Running Dagger with self-signed certificates


This documentation is for an older version of Dagger, which is no longer actively maintained.

We encourage you to upgrade and refer to the documentation for the most current version.

If you cannot upgrade to the latest version, please contact us in the help forum on Discord. When contacting us, please let us know why you cannot move to the latest version. From there, our team will work with you on your use case.

The connection to a container registry or to a remote docker daemon might require the need to add self-signed CA: x509: certificate signed by unknown authority.

These operations are being run inside the buildkitd context and require you to mount your certificates inside your buildkit instance.

Running a custom buildkit in Docker

To run a customized Buildkit version with Docker, this can be done using the below command. You can add as many certificate as you need:

docker run --net=host -d --restart always -v $PWD/my-cert.pem:/etc/ssl/certs/my-cert.pem --name dagger-buildkitd --privileged moby/buildkit:latest

To connect your Dagger client to this custom instance, please follow these steps