#Upgrade to dagger 16.3 buildkit.sock moved?
1 messages · Page 1 of 1 (latest)
I see this in the logs:
time="2025-03-14T18:44:00Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
Upgrade to dagger 16.3 buildkit.sock moved?
👋 /var/run should be a symlink to /run in the engine container
docker exec -ti 4c2 ls -la /var/run
lrwxrwxrwx 1 root root 4 Mar 9 01:19 /var/run -> /run
Not what I am seeing inside my dagger engine pod. Let me double check.
Okay it is symlinked but there is no /var/run/dagger/
One sec and I'll provide diffs between 14 and 16.3
oh, I see the dagger folder is the one which changed..
Yeah, I am actually cofused on how it is working with 0.14 tbh. I don't seem /var/run/dagger but maybe it is there. So it should I be host mounting /var/run now?
Yes, I see the helm chart change now.
My bad. What I get for just swapping the image.
lol, np
Not sure who to tell but this will need updated. It still refs /var/run/dagger https://docs.dagger.io/ci/integrations/gitlab/
Dagger provides a programmable container engine that allows you to replace your YAML pipeline definitions in GitLab with Dagger Functions written in a regular programming language. This allows you to execute your pipeline the same locally and in GitLab, with the additional benefit of intelligent caching.
Nevermind. Ignore that, the helm chart still mounts it correctly.