-
Bug
-
Resolution: Unresolved
-
Critical
-
None
I've tried
dockerImage.inside {
sshagent([...]) {
sh '...'
}
}
and this appears to fail because the ssh-agent gets launched but then the next command
appears to be ssh-agent -k which kills the process before the sh step has a chance to run despite the sh command being inside the sshagent block.
And also
sshagent([...]){
dockerImage.inside {
sh '...'
}
}
fails (I think) for a more predictable reason: the ssh-agent stays running and the env variables get
set correctly inside the container, however the socket is in /tmp on the container server which is not visible to the container (by default).
- blocks
-
JENKINS-36997 sshAgent {} inside docker.image().inside {} does not work with long project name
- Resolved
- is duplicated by
-
JENKINS-50104 ssh-agent is killed after first use in docker container
- Open
- relates to
-
JENKINS-64910 Hang when using ssh after upgrade to ssh-agent 1.21
- Closed