Erik Sipsma

> I realize that's kind of already the case, you only mention the user-facing CLI but without going in detail. I'll update the title for clarity. Thanks, yeah sorry for...

> will the helper also handle provisioning of the runner (buildkit) container? @shykes This is still a pretty open question, have gone back and forth, but my current updates to...

Getting into more implementation details now: how do we actually connect SDKs with the local engine? The stdio conn approach had a few problems, just got a new solution just...

# Summary of what we need from each SDK cc @helderco ## Provisioner 1. SDKs will be hardcoded with an image repo + SHA of an engine release that they...

@shykes Yeah I agree that the differences come down to whether we consider the local helper binary a temporary crutch or a feature. They are two highly divergent futures even...

> This means that DAGGER_HOST effectively becomes BUILDKIT_HOST Not *literally* (`BUILDKIT_HOST` is still totally ignored by our code now), but *spiritually* more or less yes, but that also is a...

> https://github.com/moby/buildkit/blob/master/cache/refs.go#L1232-L1234 If I'm correct that this is snapshot only for a couple of calls within this function, then does this point to containerd reference counting problem? Or am I...

On a second thought, I guess there is a stopgap solution where the client maintains state on each vertex digest received and doesn't print logs for ones that have already...

I independently encountered some bugs around the parallel creation of blobs for different platforms and have a fix out for PR here: https://github.com/moby/buildkit/pull/2273 Have not tried the reproducer here to...

> I have build locally #2273 and looks like it not fix this issue. Ah okay, good to know, thanks for giving it a try