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'm running the action on a Linux Ubuntu 20.04.2 machine.
Runner version 2.276.1
The action log indicates that the key has been installed successfully, but it does not work. I have inspected the key installation path ~/.ssh, and all seems right (the files have been copied, etc.). So I continued trying to install the key manually using the files already there by running ssh-add id_rsa, and I got the error message Error loading key "id_rsa": invalid format. Examining the id_rsa file, I have discovered that the action adds a '\n' at the end of the key file that invalidates the key. After removing the line with nano and rerunning ssh-add id_rsa, everything works nicely. I also double-checked that the '\n' wasn't part of the original secret in GitHub. In my particular case, I assume the error is produced by the insertion of that trailing '\n' that invalidates the key.
Cheers,
Ramon
The text was updated successfully, but these errors were encountered:
Hi,
I'm running the action on a Linux Ubuntu 20.04.2 machine.
Runner version 2.276.1
The action log indicates that the key has been installed successfully, but it does not work. I have inspected the key installation path
~/.ssh
, and all seems right (the files have been copied, etc.). So I continued trying to install the key manually using the files already there by runningssh-add id_rsa
, and I got the error messageError loading key "id_rsa": invalid format
. Examining theid_rsa
file, I have discovered that the action adds a'\n'
at the end of the key file that invalidates the key. After removing the line with nano and rerunningssh-add id_rsa
, everything works nicely. I also double-checked that the'\n'
wasn't part of the original secret in GitHub. In my particular case, I assume the error is produced by the insertion of that trailing'\n'
that invalidates the key.Cheers,
Ramon
The text was updated successfully, but these errors were encountered: