Erik Sipsma

@aluzzardi I made a few tweaks to the approach, updated the description of the PR with how it works now. There's some ugliness remaining that I call out there; I...

@aluzzardi > We're setting DAGGER_RUNNER_HOST (so the session can work), but not DAGGER_HOST -- this should trigger the provisioning of the session, but that can't be done without the docker...

> Default provisioner would work outside of our very specific CI case, right? Yes exactly, default will still work the same before. This is only needed in our very non-default...

> See other comment -- DAGGER_HOST=bin://dagger-session should do the trick (at least in Go). When not specifying a abs/rel path, it's implied it's in $PATH (e.g. cmd.Exec("ls")). Maybe Python/Node have...

@aluzzardi Updated with: * Defaulting to `bin://` and the other fixes around path handling you suggested * It turns out that even though I couldn't find it documented anywhere, nodejs...

> Give me a moment and I'll update the Python part. Thank you @helderco! Appreciate it greatly!

> Thanks. What would be helpful is a summary of supported values for DAGGER_RUNNER_HOST. I'm guessing it's a URL? If so, what schemes are supported and what do they do?...

@aluzzardi > Perhaps we mount another gRPC service in containers. Or it could be a dumb HTTP POST, whatever I don't think we'd need this. If we allow an exec...

> Especially in a new encapsulating field, while making the current ones deprecated. However, I'm not entirely sure if @vito and @sipsma have considered the effect on cache that was...

Unix socket mounting should enable this now: https://github.com/dagger/dagger/pull/4025