Cloning a project doesnt respect ssh key in git config

Hi,

I’m running node-red in a docker image (https://hub.docker.com/r/nodered/node-red-docker) in version 0.20.3.

I’d like to clone an existing project from my company’s gitlab repository.

I created the gitconfig (git@…repo.git syntax), created a ssh key through node-red’s ui, added the public key to my gitlab repo).

If I press “Clone Repository” the message

Authentication failed

is shown.

docker logs mynodered shows this

31 Mar 12:16:38 - [trace] git["clone","git@SECRET:SECRET/dudu.git","."]
31 Mar 12:16:38 - [debug] git -c credential.helper= clone git@SECRET:SECRET/dudu.git .
31 Mar 12:16:38 - [debug] [err] Cloning into '.'...
31 Mar 12:16:38 - [debug] [err] Permission denied, please try again.
31 Mar 12:16:38 - [debug] [err] Permission denied, please try again.
31 Mar 12:16:38 - [debug] [err] Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
31 Mar 12:16:38 - [debug] [err] fatal: Could not read from remote repository.
31 Mar 12:16:38 - [debug] [err]
31 Mar 12:16:38 - [debug] [err] Please make sure you have the correct access rights
31 Mar 12:16:38 - [debug] [err] and the repository exists.
31 Mar 12:16:38 - [debug] rc=128

If I put the following code in my Dockerfile:

FROM nodered/node-red-docker
ARG HTTP_PROXY
RUN npm config set https-proxy $HTTP_PROXY
RUN npm install node-red-dashboard
RUN npm install node-red-admin
RUN npm install node-red-contrib-gitlab
ENV GIT_SSL_NO_VERIFY=true
COPY settings.js node_modules/node-red/settings.js
RUN mkdir ~/.ssh
RUN ssh-keyscan code.rsint.net >> ~/.ssh/known_hosts
ENV GIT_SSH_COMMAND="ssh -i /data/projects/.sshkeys/admin_node-red"

(especially the last line) the clone process works.

It seems as if node-red’s cloning procedure does ignore the ssh keys which are defined in the ui.

Best regards,

Josef

[knolleary]

Please retry with the 0.20.5 release that has now been published.

[knolleary]

Excellent - thanks for verifying.