I'm trying to clone a repo using dagger, the required key is loaded into the ssh-agent, but when the clone command is executed, it errors out with the error in the title of this post, having said that this same code works perfectly on my local system, when i try and run it on my build server using Jenkins I get this error.
#ERROR: NotFound: no ssh handler for id default
modern peak
compact prawn
👋 your code runs fine in your Dagger pipeline locally you mean?
can you validate your jenkins server has correctly set the SSH_AUTH_SOCK variable when calling your dagger pipeline?
modern peak
🙏 @compact prawn, the pipeline in question runs on a vanilla Jenkins node, which has the ssh-agent loaded on startup and the ENV var is also available on the host/node system
compact prawn
@modern peak got it. When you say "the same code works perfectly on my system", I'd assume that's using Dagger, right?
modern peak
@compact prawn yes
compact prawn
@modern peak do you have some time to jump into #911305510882513037 and troubleshoot it together there?
compact prawn
sure, np!
modern peak
ready now
compact prawn
seems like main culpirit was an outdated go SDK 🙌 . LMK in case you need help with anything else Aditya!
modern peak
@compact prawn unfortunately, after commenting the changes we made during the call the base image again gets pulled on each attempt
sharp adder
cc <@274903880343748619> if you're around since you know this flow
Just saw the ping, sorry 🙏
compact prawn
ok, in that case something is invalidating the pull for some reason. @modern peak can you help us understand what step in your pipeline is causing the image to be repulled?
trying to understand if it's a bug or something that you're particularly doing that causes the pull each time
compact prawn
ok, in that case something is invalidating the pull for some reason. <@65126777...
Basically slowly uncomment pieces of your pipeilne until we can find which instruction is the one that causes the image re-pull
modern peak
@compact prawn yep exactly my thought, let me try that and circle back here🙏
compact prawn
thx! preciate it!
compact prawn
@modern peakcurious if you found out what's causing the image to always be pulled
modern peak
@compact prawn unfortunately no, but fortunately image pull is working fine on my Jenkins node, but the problem with cloning the repo still persists there
compact prawn
<@336241811179962368> unfortunately no, but fortunately image pull is working fi...
The ssh thing? I thought we managed to bypass that one 🤔
I'm available later today if you want to troubleshoot it
compact prawn
@modern peak just checking if you need any help here 🙏
modern peak
@compact prawn thanks🙏 i will definitely need help to resolve this, but atm i swamped with work related things, so may be we can take this up next week when you have time. Thanks again for all your help
compact prawn
sure, if you have time and and you can share with me how you're doing the cloning that'd be great
in the Dagger pipeline
modern peak
@compact prawn this is the function being used
compact prawn
<@336241811179962368> this is the function being used
I see.. pretty straightforward. LMK when you have some time to troubleshoot together 😃
modern peak
@compact prawn would have time tomorrow, to debug the cloning issue?
compact prawn
yep, let's do it 🙏
modern peak
@compact prawn great i'll ping you when i get online around 8 p.m. IST
compact prawn
👍 I'll start early tomorrow so we have more overlapping
modern peak
@compact prawn please ping when you're ready
compact prawn
@modern peak I'm getting ready for a community call here. @lime helm @clear cloud by any chance any of you is around to help here?
TLDR; @modern peak is having issues to make the SSH agent auth work in Dagger while trying to clone a repo from his pipeline
modern peak
@compact prawn we can do this tomorrow if you have the bandwidth
compact prawn
sure, tomorrow I'll be open 🙌
modern peak
@compact prawn great talk to you then
compact prawn
@modern peak did you run the pipeline again? Are you still getting "unauthorized " errors when trying to clone?
can you try bumping to the last dagger SDK version and trying again?
just to rule out any possible fixes that we might have introduced lately
modern peak
@compact prawn i tried running the same piece of code that i shared with you, both on my local Macbook and my Jenkins node, both place(s) i get the same error
@compact prawn i'll try updating the dagger lib and will let you know here how things go
compact prawn
by any chance do you have any special auth configuration in your git configs to be able to clone from that repo in your machine?