-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug Report] Cannot use ssh private key in task steps #1271
Comments
I'm hitting a similar issue. It looks like the .ssh config is set to It looks like an environment variable $HOME is set to point to I guess one option would be to change the home directory in my docker image for the user /root but that feels kind of kludgy. As far as I can tell there is no environment variable to explicitly set the path of the .ssh directory. The best I could come up with so far was creating a symbolic link /tekton/home/.ssh -> /root/.ssh |
Note: we've introduced a feature-flag to disable the defaulting And we have a plan to make this the default behaviour in an upcoming release: #2013 |
Expected Behavior
We could use ssh private key in task steps in order to execute command like
git pull
orgit push
Actual Behavior
When using command like
git pull
in task steps , it shows errorsSteps to Reproduce the Problem
Flow example https://github.com/tektoncd/pipeline/blob/master/examples/taskruns/taskrun-git-ssh.yaml and just change the
args
ofconfig step
taskrun-git-ssh.yaml
Additional Info
I analysised the reason, It seems git clone will use
/root/.ssh/config
but not/builder/home/.ssh/config
and use/root/.ssh/known_hosts
but not/builder/home/.ssh/known_hosts
.SSH Credential save private key into folder of /builder/home, So ,
git command
will not use private key correctly.When I change
args
toIt works well.
The text was updated successfully, but these errors were encountered: