Hi! One possible cause is that the certs | Dagger | Page 1

exotic pier Oct 8, 2025, 3:51 PM

#

Hmm, we did think of that and our tool kills any existing dagger engine after copying over the certificates.

spice flax Oct 8, 2025, 3:52 PM

#

that's a serious wrapper 🙂

Unrelated to your issue but i'm very interested in that wrapper, specifically in what gaps we can fill in dagger to kill the wrapper.

#

Since in the long run the UX is always better when you don't need to wrap it.

spice flax Oct 8, 2025, 3:53 PM

#

exotic pier Hmm, we did think of that and our tool kills any existing dagger engine after co...

does it remove the container or only stop it?

exotic pier Oct 8, 2025, 3:53 PM

#

docker rm -vf dagger-engine-v0.18.19

#

which should stop and remove the container entirely

spice flax Oct 8, 2025, 3:57 PM

#

indeed

exotic pier Oct 8, 2025, 3:59 PM

#

Can I view any logs to confirm that dagger-engine is checking for those certificates?

spice flax Oct 8, 2025, 4:00 PM

#

cc <@&946480760016207902>

exotic pier Oct 8, 2025, 5:30 PM

#

I figured it out: https://github.com/dagger/dagger/pull/11206

GitHub

Update custom CA configuration instructions by joemccall86 · Pull ...

Clarify the locations for writing custom CA certificates on different operating systems.
I ran into this while trying to get my coworker's macOS machine set up with dagger.

#

All my testing had the certificates in ~/.config/dagger/ca-certificates. That only works in Linux.

spice flax Oct 8, 2025, 5:48 PM

#

Nice. So you and your coworker were using different host OS?

#Hi! One possible cause is that the certs