Comment by cedws
5 months ago
Thanks for your reply. We use BuildKit's cache + SSH socket mounts in most of our Dockerfiles so this was a blocker I came up against immediately when trying Dagger. I'd rather not share my username here but there's a conversation on Discord last month you can dig up (search buildkit in:general) to see what was discussed and proposed solutions.
RE the part about not supporting Dockerfiles - sorry, that was incorrect, I misremembered.
Ah, I see the discussion thread on Discord, thanks.
It looks like you encountered a gap in the Dockerfile compatibility bridge, specifically lack of support for `--mount=type=ssh` [1]. It's true that our Dockerfile compat layer has more gaps than the native Dagger API itself. In effect, beyond very simple Dockerfiles, to get the full benefit of Dagger you need to convert them to code targeting the Dagger API. While there are many benefits to this, it does add significant friction to getting started.
It seems like we need to beef up our compatibility story!
Thanks for taking the time to share all this feedback, and sorry again that your experience didn't work out.
[1] https://github.com/dagger/dagger/issues/6736