Alternative services v2 ideas

[upbeat creek]

Also, with nesting this would mean LLB/FooIDs coming from the nested Dagger would embed both search domains (parent + child). (So really N domains as nesting increases.)

[round orbit]

Yeah agree at this point I think it's worth seeing if there's anything that's easier to upstream, I get the feeling that they probably won't a full design of full blown configurable network dependencies, which just isn't what we were going for there.

That idea sounds good at first glance, though I am now wondering how we'd implement custom DNS settings for the HTTP/Git sources since those execute not in containers but right on the buildkit host

[upbeat creek]

Same way it's already implemented in the PR, just a different way of communicating the same config to them

[round orbit]

Also, just something to keep in the very far back of our pocket, worker.Worker is an interface, so we can always provide our own implementation that wraps LLB ops if nothing else works

[round orbit]

Ah got it, I forgot about that part, makes sense

[upbeat creek]

Yeah, I was hoping to end up with an extension point for more things later (like TLS). TBH it'd be nice to just know what they think of the whole thing instead of having to guess, but having been on the other side of this interaction too, I'm guessing there are just a lot of spinning plates and they need to choose their battles

I even offered pieces to cut out, but no response

[round orbit]

I think the best hope to get a response is to explicitly tag Tonis so he gets a notification, either on github or slack or both. I know it's not always polite to constantly ping, but at this point seems reasonable