This is a base image for Docker, which includes JDK and the Jenkins agent executable (agent.jar). This executable is an instance of the Jenkins Remoting library. JDK version depends on the image and the platform, see the Configurations section below.
❗ Warning! This image used to be published as jenkinsci/slave and jenkins/slave. These images are now deprecated, use jenkins/agent.
See GitHub releases for versions 3.35-1 and above.
There is no changelog for previous versions, see the commit history.
Jenkins remoting changelogs are available here.
This image is used as the basis for the Docker Inbound Agent image. In that image, the container is launched externally and attaches to Jenkins.
This image may instead be used to launch an agent using the Launch method of Launch agent via execution of command on the master. For example on Linux you can try
docker run -i --rm --name agent --init jenkins/agent java -jar /usr/share/jenkins/agent.jarafter setting Remote root directory to /home/jenkins/agent.
or if using Windows Containers
docker run -i --rm --name agent --init jenkins/agent:jdk11-windowsservercore-ltsc2019 java -jar C:/ProgramData/Jenkins/agent.jarafter setting Remote root directory to C:\Users\jenkins\Agent.
Starting from Remoting 3.8 there is a support of Work directories, which provides logging by default and change the JAR Caching behavior.
Call example for Linux:
docker run -i --rm --name agent1 --init -v agent1-workdir:/home/jenkins/agent jenkins/agent java -jar /usr/share/jenkins/agent.jar -workDir /home/jenkins/agentCall example for Windows Containers:
docker run -i --rm --name agent1 --init -v agent1-workdir:C:/Users/jenkins/Work jenkins/agent:jdk11-windowsservercore-ltsc2019 java -jar C:/ProgramData/Jenkins/agent.jar -workDir C:/Users/jenkins/WorkThe image has several supported configurations, which can be accessed via the following tags:
- Linux Images:
latest(jdk11,bullseye-jdk11,latest-bullseye-jdk11,latest-jdk11): Latest version with the newest remoting and Java 11 (based ondebian:bullseye-${builddate})latest-jdk8(jdk8,bullseye-jdk8,latest-bullseye-jdk8): Latest version with the newest remoting (based ondebian:bullseye-${builddate})alpine(alpine-jdk11,latest-alpine,latest-alpine-jdk11): Small image based on Alpine Linux (based onalpine:${version})alpine-jdk8(latest-alpine-jdk8): Small image based on Alpine Linux (based onalpine:${version})archlinux(latest-archlinux,archlinux-jdk11,latest-archlinux-jdk11): Image based on Arch Linux with JDK11 (based onarchlinux:latest)bullseye-jdk17-preview(jdk17-preview,latest-bullseye-jdk17-preview,latest-jdk17-preview): Preview JDK17 version with the newest remoting (based ondebian:bullseye-${builddate})
From version 4.11.2, the alpine images are tagged using the alpine OS version as well (i.e. alpine ==> alpine3.15, alpine-jdk8 ==> alpine3.15-jdk8).
- Windows Images:
jdk8-windowsservercore-1809: Latest version with the newest remoting and Java 8 (based oneclipse-temurin:8.xxx-jdk-windowsservercore-1809)jdk8-nanoserver-1809: Latest version with the newest remoting with Windows Nano Server and Java 8 (based oneclipse-temurin:8.xxx-jdk-nanoserver-1809)jdk11-windowsservercore-1809: Latest version with the newest remoting and Java 11 (based oneclipse-temurin:11.xxx-jdk-windowsservercore-1809)jdk11-nanoserver-1809: Latest version with the newest remoting with Windows Nano Server and Java 11 (based oneclipse-temurin:11.xxx-jdk-nanoserver-1809)jdk17-windowsservercore-1809: Latest version with the newest remoting and Java 17 (based oneclipse-temurin:17.xxx-jdk-windowsservercore-1809)jdk17-nanoserver-1809: Latest version with the newest remoting with Windows Nano Server and Java 17 (based oneclipse-temurin:17.xxx-jdk-nanoserver-1809)
The file docker-bake.hcl defines all the configuration for Linux images and their associated tags.
There are also versioned tags in DockerHub, and they are recommended for production use. See the full list here