SSH Agent

SSH Agent is a Docker-based remote build node that lets the Jenkins controller securely connect over SSH (Secure Shell) and run jobs on a separate machine.

  • Development
  • Tools & Utilities
SSH Agent is a Docker-based remote build node that lets the Jenkins controller securely connect over SSH (Secure Shell) and run jobs on a separate machine. It is for teams that want to move builds, tests, and other automated tasks away from the controller, keeping the main system organised and reducing its load.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

57/100 Fair

Maintained
60last commit 156 days ago
Popular
631,487 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM
Security check
60no serious findings, 2 minor, CI, OpenSSF Scorecard 3.3/10
GitHub stars
1,487
Open issues
62
Last commit
2026-06-18
Latest release
v0.10.0
License
MIT
Activity
stale

Checked 18 days ago - source: GitHub (webfactory/ssh-agent)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 300 MB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add the SSH (secure shell) public key Set JENKINS_AGENT_SSH_PUBKEY to your SSH public key when starting the container. Without it Jenkins cannot sign in, and the agent will be unreachable even if the container is running. source
  • Expose the SSH port for Jenkins Add --publish 2200:22, or another free port on your computer to container port 22, to the command that starts the container. If you skip it, the container's SSH port is hidden, so Jenkins cannot connect from your machine. source
  • Pre-add known hosts for git servers Add JENKINS_AGENT_SSH_KNOWNHOST_0, JENKINS_AGENT_SSH_KNOWNHOST_1, and so on for git sites you will clone from. This helps the agent recognize those servers so the first clone does not stall waiting for a server identity check. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I make the Jenkins SSH agent reachable from Jenkins?

Publish the container SSH port by mapping a host port to container port 22, such as publishing 2200 to 22. If you skip the port mapping, the container SSH port is hidden and Jenkins cannot connect.

How can I prevent the first git clone from stalling on host verification?

Pre-add git server host entries using variables such as JENKINS_AGENT_SSH_KNOWNHOST_0 and JENKINS_AGENT_SSH_KNOWNHOST_1. This helps the agent recognize those servers instead of waiting for a server identity check.

Can ssh-agent run as a service and load unencrypted keys automatically?

Yes, ssh-agent can be started as a systemd service. The referenced setup also automatically adds unencrypted keys after the service starts.

Answers sourced from github.com, github.com, unix.stackexchange.com

Community

Collected 48 days ago - public community threads