kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

Docs: 1224-self-signed-certificates

Browse Source 
Add documentation on how to use Dagger with self-signed certs

Signed-off-by: guillaume <guillaume.derouville@gmail.com>
This commit is contained in:
guillaume 2022-04-08 11:28:46 +02:00
parent 1157561f1d
commit e48262a2fb
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/guides/1224-self-signed-certificates.md Normal file
View File

@ -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)