Deeper integration with Docker tooling

[bitter sleet]

Starting a thread for this 🙂

Summarizing the discusion so far:

• Tighter integration with Docker tooling would be nice
• One idea is to make Dagger embeddable in the Dockerfile as a buildkit frontend (#syntax line at the beginning of the Dockerfile).
• Another idea is to get docker-compose to use Dagger to build, but unclear if there's an extension point for that

[stone viper]

I was looking at compose docs and there's a --builder argument - thinking of that's set to dagger; docker file becomes the function name, build args are function args; might be a cleaner way to do it; but not from reading bits and pieces on my phone

[bitter sleet]

Ah cool. I don't know this builder option. Indeed that might be an extension point we could use 🙂

There's also the "Docker SDK" that @glossy dagger is working on - did you see that?

It automatically parses your Dockerfile and Docker-compose files, and exposes them as Dagger functions you can call directly from the CLI (or from any other SDK)

[dawn ferry]

Seems like the Docker SDK would be closer in spirit to what @stone viper might be needing. 🤔

[stone viper]

The SDK might do the job; I really just want a way to unify the code with for my pipeline with the code needed to spin up a local dev environment as there's substantial overlap

Otoh if the work is done for the SDK to show dagger to spin up the contents of a docker compose file; then it's probably possible to do it manually

[dawn ferry]

That's manily the objective of the Docker SDK, to unify the experience across local environments and build pipelines

Would be great to show you what we have and work together to make the experience great