#dagger engine container name/metadata

1 messages · Page 1 of 1 (latest)

teal adder Jul 1, 2024, 4:36 AM

Hello, is it possible to instruct dagger sdk to attach metadata or at minimum use custom name to the executed dagger engine container?

We are trying to use dagger inside eksisting CI that is managed by other team. They require us to delete any created container and its volume when running the CI to avoid storage getting full. Having metadata or custom name could help us in deleting only the engine that was started by the specific CI job.
We would like to prevent starting separated engine manually since that require us to maintain the version used inside CI script that is separated from the code repository that holds the dagger script.

thanks

wispy beacon Jul 1, 2024, 11:44 AM

currently, there's no way to attach custom metadata - there is an ongoing conversation about how to manage the lifecycle and configuration of engines here though: https://github.com/dagger/dagger/issues/5583

GitHub

Compute Drivers · Issue #5583 · dagger/dagger

This issue was previously named "engine drivers", but "compute drivers" is proving more clear. Problem The Dagger CLI has a builtin “compute driver”: a software interface which ...

i think starting the engine yourselves is the only option at the moment sadly - you can however, grab the version from the cli using dagger version and use that version in there to download the right engine version so you don't need to store it separately