#Dagger Cloud
neon adder
Are you putting custom CA certs in /usr/local/share/ca-certificates in the engine you are building against?
I can build off main fine
tawdry sluice
I tried on main, same issue :/
neon adder
What engine are you running against? If it's v0.18.11 what is the output of docker exec -it dagger-engine-v0.18.11 ls /usr/local/share/ca-certificates
tawdry sluice
Trace from ./hack/dev on main (not with --cloud)
docker exec -it dagger-engine-v0.18.11 ls /usr/local/share/ca-certificates
orbstack-root.crt
okay, not sure why orbstack is installing CA certs into the engine...? but that aside, that's why you are hitting it but not me
tawdry sluice
Alex also isn't hitting that problem
neon adder
https://docs.orbstack.dev/features/https#between-containers I'd disable that
tawdry sluice
I tried to wipe the cache, didn't help, that's the first time I'm hitting that error
neon adder
Yeah there was a change to the engine build which is causing this to bubble up for you now, but it would only happen if there are custom CA certs installed in the engine, which is only happening for you because Orbstack decided to do that automatically for some reason
I'll look at fixing it in the engine build but in the meantime I'd disable orbstack from doing that since it's probably slowing everything down for you a ton
I actually wonder if this partially explains why things are so much slower on macos than linux... since even though it's causing an error for the first time now it's probably been slowing the engine down for you for a long time
tawdry sluice
I'll deactivate it and tell you if it fixes + speed things up haha
tawdry sluice
Ok it fixed the problem by creating an engine manually with the deactivate certs
Thanks a lot Erik! I don't know how you found that haha
neon adder
np, it's just related to what I did yesterday. I'll fix the bug and probably also push a change to ignore orbstack-root.crt so you don't have to manually create the engine after the next release
tawdry sluice
Thanks! 