#Anyone using Dagger with Concourse CI

1 messages · Page 1 of 1 (latest)

wraith vault
#

Guessing we'd need a Concourse task for running dagger do <action name>?

#

I haven't played with Concourse in a while, but would love to help bring this to life 🙂

glad sonnet
#

Exactly! Yeah it's something I'd like to get working (since we use Concourse where I work and it would help me get dagger "in the door"), but wanted to see if anyone had developed any good patterns already. It could be a very straightforward thing to implement. Not sure if any special considerations are needed around buildkit in the Concourse context

tiny beacon
#

If you’ve no buildkit infra, then you’d need the tasks to run in privileged mode.

#

I don’t recall if there’s any mechanism in concourse for standing up a (buildkit) daemon in one task, say at the start of a concourse DAG, letting other concourse jobs use it by announcing its location somehow (maybe pass it as a resource version?) and terminating it gracefully at the end.

glad sonnet
#

Great notes Jonathan, thank you!

To your point about standing up a buildkit daemon, I've seen that concourse/oci-build-task exists, but have yet to take it for a spin and am not sure about how fully and satisfyingly it might enable long-running buildkit across DAG steps:

https://github.com/concourse/oci-build-task

The code example here looks like it could be a good starting point for what a simple concourse-dagger proof-of-concept might look like:

https://github.com/concourse/oci-build-task#migrating-from-the-docker-image-resource

Maybe adding dagger to the above could be a matter of having that build task run in an in_parallel block alongside a second task that runs dagger do?