Are there any sort of deploy docs

[hallow quartz]

Earlier in v0.3.2, I was able to setup and connect to a remote buildkit and spin up dagger engine locally. It worked great. There are some changes since then but looks like maintainers do want to support this use-case

[lyric nebula]

Right, and I think the ticket @shut island tracks making sure it still works it seems?

Also re: containers, I have found this – https://github.com/dagger/dagger/issues/2398 – but it doesn't seem to be exposed in non-CUE SDKs. This seems to imply you won't need Docker to run containers, only BuildKit? Or am I misunderstanding this?

[hallow quartz]

It doesn't work in v0.4.0 but yeah, that issue will most likely give us an outcome

I don't know about the cue issue you pointed.

[wraith solar]

The issue you point to is more about to start other containers during the pipeline (setup some test db for e2e testing for example)
For now, we stopped the ability to connect to another instance of buildkit directly as it created hard to debug bugs. We will eventually have a solution about that, but we were focusing on the most important SDK. We'll go back to fix those issues.

(oh, just saw the answer from @shut island)

[lyric nebula]

@wraith solar yeah, I kind of had two questions – one about remote BuildKit, which this answers – but also about whether for running containers like this you need anything other than just BuildKit?

I can't seem to find how that issue relates to what is currently in the SDKs either

Why I'm asking is that technically with Docker image builds you can actually run sidecar containers if you create the network yourself (we're doing that for one of our builds that needs to pregenerate CSS) and was curious whether it's something you will want to support and if so, will it work with only BuildKit, or would it have additional requirements.

[wraith solar]

So, we used to use docker to bootstrap a buildkitd container that we would connect to.
We had to change all of that, but in the background, it is still buildkit that runs.
Buildkit could run some containers, but we don't expose that API (yet). It is clearly an often asked demand. So we will get there eventually, but we need to fix other tasks first.

I think there was some way to pass the docker socket file into your pipeline so you could run docker command from there. It's a hack for now, and I don't know where we documented it.