I'm testing out dagger in self-hosted | Dagger | Page 1

leaden whale Oct 22, 2024, 7:41 AM

#

if you didn't read already you can read the thread above (#1296119797167292518 message) it seems your concern is similar as well

uneven sapphire Oct 22, 2024, 8:30 AM

#

Thanks, I did see that but I don't think applies as I am not using temporary dagger enigines in docker. Instead I have setup a permanent dagger enginge in k8s and I am using _EXPERIMENTAL_DAGGER_RUNNER_HOST=unix:///var/run/dagger/buildkitd.sock in the config so it should connect to that dagger engine. Maybe I need to double check that it is actually using the k8s installed dagger engine from gitlab.

#

Tried it without pointing it to the k8s installed dagger engine and in that case I got error ! failed to run command: exec: "docker": executable file not found in $PATH . So I think it is actually using the dagger engine running in k8s.

uneven sapphire Oct 22, 2024, 9:30 AM

#

The relevant code is .withMountedCache("/root/.npm", dag.cacheVolume("node")) . I am not sure what "node" is here, it is a cache key, but what is the scope of that key?

#

Perhaps it is somehow scoped to each run in gitlab and gets recreated each time?

#I'm testing out dagger in self-hosted