#Is it possible to use buildkit with python SDK ?
1 messages · Page 1 of 1 (latest)
Hi, what do you mean by “use buildkit”? The dagger engine is powered by buildkit so if you use dagger, you automatically use buildkit.
If we have our own buildkit setup then do we need a docker engine? Because i tried it but didn't work
You can still connect to your own buildkit but that feature will be deprecated eventually in favor of connecting to your own dagger engine (which bundles buildkit along with other components in a tightly coupled way)
do you have any deployment guide of dagger engine ?
Not yet, we are working on that feature. Until it’s ready you can still connect to your own buildkit by setting an environment variable
(can’t remember the name of the variable at the moment)
you can set DAGGER_RUNNER_HOST to make your SDK talk to a different buildkit engine. Can't recall if using an external buildkit is fully working currently given our shims
It didn't work with my buildkit but it worked with the dagger engine perfectly.
Any Tips for deploying the dagger engine in Kubernetes? Is there any difference in deployment or is it the same as buildkit?
@fringe basin this is still work in progress. At the moment the engine is in 2 parts: API router, and runner. The runner can run remotely on any OCI-capable system (including kubernetes node), but the router must run locally. We are working to change that, so that both router and runner can run together on OCI (and thus kubernetes).
For now, you can still deploy the runner on kubernetes. Under the hood it is powered by buildkit, so any method for deploying buildkit on kubernetes will also work for the Dagger runner. Just replace BUILDKIT_HOST with _EXPERIMENTAL_DAGGER_RUNNER_HOST and it should work