limber plume
We manually manage our engine because of a requirement that images must be hosted internally. This adds a lot of work on our end compared to say being able to just swap out the registry that Dagger auto starts the image from.
Is there such an ENV var? Any other ideas come to mind, like maybe fooling it with DNS or http proxy shenanigans?
limber plume
Ideally, there is something in between where I can say DAGGER_ENGINE_IMAGE_REGISTRY=us-central1-c... and Dagger will do the same version matching / GC without me needing to manually manage the engine container
we do that manual container management in ansible, but that doesn't work for multiple version where we may need to switch depending on the branch running in CI
slow dirge
I see what you mean. I think custom registries cover what you want here? https://docs.dagger.io/reference/configuration/engine/#custom-registries
oh wait.. that's not for the engine image but the images pulled by dagger pipelines
well.. you can set this at your container runtime level
all container runtimes support that
limber plume
right! forgot about that setting
