Chainguard Container for jenkins-inbound-agent

The Jenkins Inbound Agent container image is designed to run as a Jenkins agent that connects to a Jenkins controller via inbound (JNLP) connection method, used in Jenkins Kubernetes setups.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/jenkins-inbound-agent:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This image is comparable to the jenkins/inbound-agent image available from Docker Hub. Switching to the Chainguard image should not require any changes to your existing Jenkins setup.

Getting Started

Docker

You can run the Jenkins Inbound Agent with Docker:

docker run --init cgr.dev/ORGANIZATION/jenkins-inbound-agent -url http://jenkins-server:8080 <secret> <agent-name>

Kubernetes with Helm

The most common use case for this image is within Kubernetes. You can use the official Jenkins Helm chart with the Chainguard Jenkins Inbound Agent image:

1. Add the Jenkins Helm repository:

helm repo add jenkins https://charts.jenkins.io
helm repo update

2. Create a values.yaml file to configure the deployment with the Chainguard image:

agent:
  enabled: true
  image:
    repository: cgr.dev/ORGANIZATION/jenkins-inbound-agent
    tag: latest
    alwaysPullImage: true
  resources:
    requests:
      cpu: "256m"
      memory: "256Mi"
    limits:
      cpu: "512m"
      memory: "512Mi"

# Additionally, if you wish to use the Chainguard Jenkins image:
controller:
  image:
    registry: cgr.dev
    repository: ORGANIZATION/jenkins
    tag: latest

3. Install the Jenkins Helm chart:

helm install jenkins jenkins/jenkins \
  --values values.yaml \
  --namespace jenkins --create-namespace

JCasC Configuration

If you're using Jenkins Configuration as Code (JCasC), you can configure pod templates to use the Chainguard Jenkins Inbound Agent:

jenkins:
  clouds:
    - kubernetes:
        name: "kubernetes"
        templates:
          - name: "jenkins-agent"
            namespace: "jenkins"
            label: "jenkins-agent"
            nodeUsageMode: NORMAL
            containers:
              - name: "jnlp"
                image: "cgr.dev/ORGANIZATION/jenkins-inbound-agent:latest"
                alwaysPullImage: true
                privileged: false
                resourceRequestCpu: "256m"
                resourceRequestMemory: "256Mi"
                resourceLimitCpu: "512m"
                resourceLimitMemory: "512Mi"
                workingDir: "/home/jenkins/agent"
            idleMinutes: 30
            podRetention: "OnFailure"

Environment Variables

The image respects the following environment variables:

• AGENT_WORKDIR: Path to the agent's work directory (default: /home/jenkins/agent)
• JENKINS_URL: Jenkins controller URL
• JENKINS_SECRET: Agent connection secret
• JENKINS_AGENT_NAME: Agent name
• JENKINS_WEB_SOCKET: If true, use WebSocket transport for JNLP (default: false)

Documentation and Resources

• Official Jenkins inbound-agent repository
• Jenkins Kubernetes Plugin Documentation
• Jenkins Helm Chart Documentation

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.