dockerBuild - failed to verify certs | Dagger | Page 1

spice elbow Oct 2, 2023, 7:06 PM

#

I am trying to do a dockerBuild but It's throwning an error at the "FROM" when it tries to pull an image from a public docker registry. I dont' have this issue when pulling the same from container().From(). I haven't had to set add my root CA to the dagger engine. Since the DockerBuild command is attached to Directory I don't have a way to do registry auth either and it doesn't look like my current auth context is passed into the DockerBuild.

spice elbow Oct 3, 2023, 4:32 PM

#

Looks like I am getting the same error with container().From() for that image too. So this is directly related to https://github.com/dagger/dagger/issues/4217.

GitHub

Issues · dagger/dagger

A programmable CI/CD engine that runs your pipelines in containers - Issues · dagger/dagger

boreal ice Oct 4, 2023, 8:11 AM

#

@spice elbow just to double check, you're getting errors with both container.from()and dockerBuild opreations right?

#

so basically what you need is to setup the certs in the engine?

#

until we have the bandwidth to work on 4217, you have alternatives to needing to maintain a custom engine. So basically:

https://github.com/dagger/dagger/issues/4217#issuecomment-1691922162
You can use the official engine image and mount the secrets at engine bootup time as described here: https://github.com/dagger/dagger/blob/main/core/docs/d7yxc-operator_manual.md#custom-ca-certs

spice elbow Oct 5, 2023, 4:10 PM

#

is probably something I will try. (Feels very hacky)
Is basically creating a custom image so I'd like to stay away from it.

So, chances are, I'll have to wait for #4217 😦

#

I've bumped the issue as a priority for us.

#dockerBuild - failed to verify certs