Justin Chadwell

Hey, sorry this has sat for so long - I tried to get some stuff kickstarted in #6288, to provide the foundations for this work (I'll try and kick that...

One other thought about this - one of the big open questions around drivers for me is how we should handle lifetimes. Who manages an engine's lifetime? - Does the...

Just had a scratch idea, could we do all the CRI magic *without* needing a huge engine refactor? The thing we didn't like before was the idea of doing lots...

Potentially it's this simple: - CLIs create dagger engines, with a timeout parameter - After the engine has exceeded a timeout without a new connection, it shuts itself down (this...

I think there's two pieces of work here that are both important to clarify: - The compute drivers work - this allows the CLI to have pluggable components that allow...

Synced with @gerhard, just wanted to write up some of my notes: - Agreed that the purpose should be to provide an agnostic way of provisioning dagger engines - not...

This PR should now be ready to review, it's not 100% feature complete, since it's missing other language support, but IMO it's a good enough starting point to get in.

Woo, think I've really got the edge cases now. I've also split it out into smaller commits to make it easier to review.

I think this is now resolved 🤔 There was a MacOS issue resolved in https://github.com/dagger/dagger/pull/9484, but the issue from here seems to have been fixed some time ago!

> The sequencing I'm imagining which incorporates both connecting and then provisioning > > We make the hook for getting connections (what's called `_EXPERIMENTAL_DAGGER_RUNNER_HOST`) public and documented I'm good with...