From e48262a2fb4228c1fe37310c33bdf938ea7573c0 Mon Sep 17 00:00:00 2001 From: guillaume Date: Fri, 8 Apr 2022 11:28:46 +0200 Subject: [PATCH] Docs: 1224-self-signed-certificates Add documentation on how to use Dagger with self-signed certs Signed-off-by: guillaume --- docs/guides/1224-self-signed-certificates.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 docs/guides/1224-self-signed-certificates.md diff --git a/docs/guides/1224-self-signed-certificates.md b/docs/guides/1224-self-signed-certificates.md new file mode 100644 index 00000000..9bcb44f3 --- /dev/null +++ b/docs/guides/1224-self-signed-certificates.md @@ -0,0 +1,19 @@ +--- +slug: /1224/self-signed-certificates/ +--- + +# Running Dagger with self-signed certificates + +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: + +```shell +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](../guides/1223-custom-buildkit.md)