You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think one problem may be if /home/docker/.ssh/id_ed25519 is the default key path, in which case rig could assume that an explicit keypath wasn't given and tries other methods 🤔 If a keypath is given, it should only try that key and nothing else.
While debugging a
k0sctl
issue, I found my specifiedkeyPath
for ssh is not used and ssh connection failed.To work around the issue, I had to manually add the key to ssh agent or unset
SSH_AUTH_SOCK
or clearing keys in ssh agent.I reviewed
k0sproject/rig
codes and found the reason is that I have already had other ssh keys in SSH agent, and the specified ssh key file is configured as anotherssh.AuthMethod
in https://github.com/k0sproject/rig/blob/v0.19.0/ssh.go#L434 , sossh.ClientConfig.Auth
has twoAuthMethod
, bothmethod(
) ispublickey
,golang.org/x/crypto/ssh client_auth.go
only tries the first one for the same auth method (https://cs.opensource.google/go/x/crypto/+/refs/tags/v0.29.0:ssh/client_auth.go;l=101), so the specified ssh key file is never used.The text was updated successfully, but these errors were encountered: