#x509: certificate signed by unknown authority

1 messages · Page 1 of 1 (latest)

solemn meadow
#

I kinda got stuck during the get started guide 😦
At my company we use Netskope and it has proven to be the worse nightmare for any developer, for every tool we use we need to provide the tool with a "custom" ssl certificate so the request can actually work... anyway I'm just wondering if anyone has faced that issues before or if we have the ability to pass a custom tls certificate to dagger engine.
This is the error I get when trying the fetch go docker from docker.io

Establishing connection to Engine... OK!
5: resolve image config for docker.io/library/golang:1.19
5: > in from golang:1.19
5: resolve image config for docker.io/library/golang:1.19 ERROR: failed to do request: Head "https://registry-1.docker.io/v2/library/golang/manifests/1.19": tls: failed to verify certificate: x509: certificate signed by unknown authority
panic: input:1: container.from failed to do request: Head "https://registry-1.docker.io/v2/library/golang/manifests/1.19": tls: failed to verify certificate: x509: certificate signed by unknown authority

Thanks for the awesome tool by the way, the idea is brilliant!!

solemn meadow
#

If anyone has the same issues this is what I run (it's just a initial test so haven't made that look good ahha yet)

CUSTOM_ENGINE_NAME="dagger-engine.dev"

docker run
-d
-v $SSL_CERTS:/ssl
-e SSL_CERT_FILE=/ssl/nscacert.pem
-v ${CUSTOM_ENGINE_NAME}:/var/lib/dagger
--name ${CUSTOM_ENGINE_NAME}
--privileged
ghcr.io/dagger/engine:main
--debug

export _EXPERIMENTAL_DAGGER_RUNNER_HOST="docker-container://${CUSTOM_ENGINE_NAME}"

dense abyss