#Remote dagger-engine
1 messages · Page 1 of 1 (latest)
Hi, I'll let my colleagues answer, I'm not sure anymore, at the moment, with all the changes on the engine 😇 However, I'll make sure they see the question 🙏
@stable oar, I don't think it's the case isn't it ?
this comes up a lot as a discussion point internally, and might be technically possible after recent changes but I don't think it's documented or supported yet. @indigo vapor would have a more confident answer 🙂
We're working on figuring out how we want to officially support custom engines + custom provisioning: https://github.com/dagger/dagger/issues/4105
In the mean time, let us know what specifically you would want from a "remote" dagger engine. Details like where you want to run it, how you want to set it up, etc. would be extremely helpful
I'm asking that because today i spent a lot of time waiting for piepline because my GHA workflow was spawing a new dagger engine every run so i couldn't profit from the cache
I'm expecting something setting like DAGGER_URL=https://my-dagger-host.fr
I see, makes perfect sense. For your use case, is it important that you have control over the dagger engine and the infra it runs on? Or would a managed engine that the dagger team runs for you work just as well?
I would like to have both possibility. If running my own dagger engine is too painful going to managed would be a plus
I think this feature too much potential. At least for me it solves multiple problems.