past crest
Forgive the naive question, I'm a lifelong mac/linux user but now in the position of doing ops for a team that includes windows users!
I'm curious about using Dagger's Git Integration from windows; while I could perhaps ask our windows devs to run code in the WSL, I wanted to check if anyone has tried running it using the native SSH-Agent?
verbal pier
Seems like buildkit has the ability to do it (https://github.com/moby/buildkit/blob/master/session/sshforward/sshprovider/agentprovider_windows.go) , but Dagger doesn't handle windows bits and pieces yet. cc @brittle tinsel no sure how much work would be needed to also support windows named pipes as a Socket type in Dagger
brittle tinsel
There has been slow but steady progress on supporting windows in buildkit (and containerd) over the years: https://github.com/moby/buildkit/issues/616
In fact I’ve seen quite a few PRs just in the last few weeks related to windows support. But overall it still isn’t totally functional afaik, just a WIP.
So running in WSL is going to be a much better bet right now I think
past crest
Thanks, that's a very clear answer! Indeed, I'll focus on WSL; our main windows devs either use it already or would be happy to, they're not married to windows-native.
verbal pier
@brittle tinsel I wasn't thinking about buildkitd but buildctl and the ability for users to start builds from windows. We're currently distributing a dagger windows binary as well, but some things like WithUnixSocket particulary for sshauthentication doesn't work there. From the code I posted above, seems like client-side SSH session handling should be able to work in Windows, correct?