#Would it be totally weird if dagger
1 messages ยท Page 1 of 1 (latest)
Basically I have a project I'd like to use from dagger but the project outputs raw LLB (or at least the go representation for my purposes).
We were discussing that recently ๐ Some sort of buildkit bridge would be nice. Not sure we'd want to expose it in the core API though
Another approach would be to run buildkit itself as a dagger service - except it would be modified to make dagger calls in the backend (using dagger-in-dagger support)
main benefit is that no changes to the core API are required
Also considered that as well ๐
IMO whoever gets that ball rolling, will find that a lot of people are interested to join the fun (myself included)
same for Docker Engine compat btw
I'm not 100% if all the dots actually connect, but we do support running dockerfiles already. And in dockerfiles you can specify a custom directive at the top to use a different frontend image. So if there was a frontend image where you just loaded up some serialized LLB and solved it, then maybe this would already work today?
I might be misremembering the details as to how that syntax directive works, but I think something along these lines would work
(side note, having written said project that outputs LLB, the dagger API is much nicer to work with)
corollary: if your target is already available as a buildkit frontend, we could probably add support for arbitrary frontends, too