#yes, that should be ok. It's also not
fair gale
I'm not following. Doesn't Dagger need a Docker socket?
no it doesn't. Dagger has its own container runtime
we use Docker to provision the engine locally in your machine but when running in k8s that's not necessary since the engine runs as a pod
eternal gale
Fair enough, you only need Docker to provision the engine locally. But I thought this was what OP was trying to achieve? (Run Dagger inside jobs triggered by Jenkins and executed in some ephemeral k8s pods.)
Either way, even if you run the engine as separate pod (i.e. separate from the ephemeral Jenkins job's pod), you will still have to face the question of how to nest containers, won't you? After all, the engine pod will be executed by k8s's OCI runtime and then it will try to spawn containers on its own. My understanding from what you wrote is that if the engine's k8s pod is not privileged (possibly even rootless) and runs with a regular (not VM-backed) OCI runtime like runc or crun, this will likely be difficult or impossible, but a VM-backed runtime should be ok?
fair gale
Either way, even if you run the engine as separate pod (i.e. separate from the e...
Yes, that's correct