Failed to run git on step ModuleSource

[finite moat]

Hello,
When I try the Quickstart, by calling the first function "hello", I receive this error message in the first step:

x initialize
  x moduleSource(refString: "github.com/shykes/daggerverse/hello@v0.1.2")
Error: failed to get configured module: failed to get module ref kind: input: moduleSource get git tags: failed to run git: exit status 128

I'm in a controlled environment, I can't replicate in my personal computer, so I think it's a connectivity issue. Is that step launched on the dagger engine container or another image ?

[stray flower]

Hi @finite moat! Pulling the module happens within the context of the dagger engine. For example, if you do dagger -m github.com/shykes/daggerverse/hello@v0.1.2 functions in your local computer while looking at the logs of the dagger-engine container you will find this:

time="2024-03-12T16:34:59Z" level=debug msg="http handler for client conn to path /query" client_call_digest= client_hostname=pop-os client_id=v1tfcndthiv1ega1a2h2sw1l2 server_id=2voxfjpxnzgzh8199x8cezx5o spanID=77decb3c7c16d27a traceID=75c5e6ec9802f1d18d228d70ad0260a0
Initialized empty Git repository in /var/lib/dagger/runc-overlayfs/snapshots/snapshots/1098/fs/
3d608cb5e6b4b18036a471400bc4e6c753f229d7        refs/tags/hello/v0.1.2
From https://github.com/shykes/daggerverse
 * [new tag]         hello/v0.1.2 -> hello/v0.1.2
time="2024-03-12T16:35:01Z" level=debug msg="http 

[analog spade]

^ this. @finite moat. So basically you should have a dagger-engine container and dagger images in your machine after running dagger call. It's very likely that's a connectivity issue as you're mentioning

[finite moat]

Thanks perfect, I forgot to check logs

This comes from the custom CA: SSL certificate problem: self-signed certificate in certificate chain.
I added it to /etc/ssl/certs in the container dagger engine, and launched the command update-ca-certificates, however it seems it's not enough. I will troubleshoot more tomorrow