[JENKINS-71537] ssh-add is timing out in a Fargate worker

[jenkins-infra-bot]

I have a Jenkins instance which spins up workers in Fargate. However, the following occurs when I try to run sshagent:
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)
SSH_AUTH_SOCK=/tmp/ssh-BX6ulrCb6Ksu/agent.163
SSH_AGENT_PID=166
Running ssh-add (command line suppressed)
ERROR: Timeout after 1 minutes
[ssh-agent] Started.[Pipeline]

{[Pipeline] sh[Pipeline] }

ERROR: Timeout after 1 minutes
[ssh-agent] Stopped.[Pipeline] // sshagent
Any idea why it might be timing out? I imagine were it failing to add the provided key, it would not be a time out, rather an explicit error no?

---

Originally reported by cestioco, imported from: ssh-add is timing out in a Fargate worker

• status: Open
• priority: Minor
• component(s): ssh-agent-plugin
• resolution: Unresolved
• votes: 0
• watchers: 1
• imported: 20260604-211335

Raw content of original issue

I have a Jenkins instance which spins up workers in Fargate. However, the following occurs when I try to run sshagent:
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Exec ssh-agent (binary ssh-agent on a remote machine)
SSH_AUTH_SOCK=/tmp/ssh-BX6ulrCb6Ksu/agent.163
SSH_AGENT_PID=166
Running ssh-add (command line suppressed)
ERROR: Timeout after 1 minutes
[ssh-agent] Started.[Pipeline] 
{[Pipeline] sh[Pipeline] }
ERROR: Timeout after 1 minutes
[ssh-agent] Stopped.[Pipeline] // sshagent
Any idea why it might be timing out? I imagine were it failing to add the provided key, it would not be a time out, rather an explicit error no?

• environment: Jenkins 2.401.1

[jenkins-infra-bot]

cestioco:

• Original comment link
• Raw content of original comment:

  I have since moved to using EC2 runners but it still happens. I think I'm bumping into the problem described here:
  Unfortunately, this means that if the Jenkins Agent was forced to create the socket in the system temp instead of the Workspace one, processes inside the container are not able to access it.
  So, I tried to solve it by mounting /tmp in container to /tmp in host. However, though the ssh socket files are now reflected in the host's /tmp, the same problem persists.
  

I have since moved to using EC2 runners but it still happens. I think I'm bumping into the problem described here:

Unfortunately, this means that if the Jenkins Agent was forced to create the socket in the system temp instead of the Workspace one, processes inside the container are not able to access it.

So, I tried to solve it by mounting /tmp in container to /tmp in host. However, though the ssh socket files are now reflected in the host's /tmp, the same problem persists.

[jenkins-infra-bot]

cestioco:

• Original comment link
• Raw content of original comment:

  This is almost certainly due to JENKINS-71556.
  

This is almost certainly due to JENKINS-71556">JENKINS-71556.