Skip to content
Docker official jenkins repo
Shell Dockerfile HTML Makefile
Branch: master
Clone or download
Pull request Compare This branch is 691 commits ahead of michaelneale:master.
daniel-beck Merge pull request #886 from daniel-beck/30-releases
Look further back to handle LTS.4/LTS.1 dual release days
Latest commit 7d1ab73 Sep 25, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Introduce Docker Packaging changelogs (#856) Jul 29, 2019
multiarch Use updated OS packages at build time (#824) May 13, 2019
tests #709,#861 - Make the REF_DIR configurable in plugin installation scri… Aug 16, 2019
tools Bump shellcheck from 0.5.0 to 0.6.0 Jul 20, 2019
.gitignore #857 - Make the Jenkins WAR path configurable by the `JENKINS_WAR` en… Aug 16, 2019
.gitmodules Add tests for Jun 27, 2016 Introduce Docker Packaging changelogs (#856) Jul 29, 2019 Add Hacking documentation Dec 12, 2018
Dockerfile Change version and checksum (#869) Aug 16, 2019
Dockerfile-alpine #709,#861 - Make the REF_DIR configurable in plugin installation scri… Aug 16, 2019
Dockerfile-centos #709,#861 - Make the REF_DIR configurable in plugin installation scri… Aug 16, 2019
Dockerfile-jdk11 #709,#861 - Make the REF_DIR configurable in plugin installation scri… Aug 16, 2019
Dockerfile-slim #709,#861 - Make the REF_DIR configurable in plugin installation scri… Aug 16, 2019
HACKING.adoc Turn on multiarch releases for jenkins4eval and extra docs (#750) Mar 7, 2019
Jenkinsfile Prevent CI timeout when Docker agents are too busy Jul 24, 2019
LICENSE.txt Fixes #475 Add LICENSE file Jul 24, 2017
Makefile #857 - Make the Jenkins WAR path configurable by the `JENKINS_WAR` en… Aug 16, 2019 #857 - Make the Jenkins WAR path configurable by the `JENKINS_WAR` en… Aug 16, 2019
docker-compose.yml add docker-compose.yml Sep 4, 2015 #709,#861 - Make the REF_DIR configurable in plugin installation scri… Aug 16, 2019
jenkins-support #709,#861 - Make the REF_DIR configurable in plugin installation scri… Aug 16, 2019 #709,#861 - Make the REF_DIR configurable in plugin installation scri… Aug 16, 2019 use $JENKINS_HOME in Mar 5, 2018 Bump shellcheck from 0.5.0 to 0.6.0 Jul 20, 2019 Look further back to handle LTS.4/LTS.1 dual release days Sep 25, 2019 Use the tini shim in all flavours Mar 11, 2018
tini_pub.gpg Prevent failures from gpg keyserver Jan 8, 2018

Official Jenkins Docker image

Docker Stars Docker Pulls Join the chat at

The Jenkins Continuous Integration and Delivery server available on Docker Hub.

This is a fully functional Jenkins server.


docker run -p 8080:8080 -p 50000:50000 jenkins/jenkins:lts

NOTE: read below the build executors part for the role of the 50000 port mapping.

This will store the workspace in /var/jenkins_home. All Jenkins data lives in there - including plugins and configuration. You will probably want to make that an explicit volume so you can manage it and attach to another container for upgrades :

docker run -p 8080:8080 -p 50000:50000 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts

this will automatically create a 'jenkins_home' docker volume on the host machine, that will survive the container stop/restart/deletion.

NOTE: Avoid using a bind mount from a folder on the host machine into /var/jenkins_home, as this might result in file permission issues (the user used inside the container might not have rights to the folder on the host machine). If you really need to bind mount jenkins_home, ensure that the directory on the host is accessible by the jenkins user inside the container (jenkins user - uid 1000) or use -u some_other_user parameter with docker run.

docker run -d -v jenkins_home:/var/jenkins_home -p 8080:8080 -p 50000:50000 jenkins/jenkins:lts

this will run Jenkins in detached mode with port forwarding and volume added. You can access logs with command 'docker logs CONTAINER_ID' in order to check first login token. ID of container will be returned from output of command above.

Backing up data

If you bind mount in a volume - you can simply back up that directory (which is jenkins_home) at any time.

This is highly recommended. Treat the jenkins_home directory as you would a database - in Docker you would generally put a database on a volume.

If your volume is inside a container - you can use docker cp $ID:/var/jenkins_home command to extract the data, or other options to find where the volume data is. Note that some symlinks on some OSes may be converted to copies (this can confuse jenkins with lastStableBuild links etc)

For more info check Docker docs section on Managing data in containers

Setting the number of executors

You can specify and set the number of executors of your Jenkins master instance using a groovy script. By default its set to 2 executors, but you can extend the image and change it to your desired number of executors :


import jenkins.model.*

and Dockerfile

FROM jenkins/jenkins:lts
COPY executors.groovy /usr/share/jenkins/ref/init.groovy.d/executors.groovy

Attaching build executors

You can run builds on the master out of the box.

But if you want to attach build slave servers through JNLP (Java Web Start): make sure you map the port: -p 50000:50000 - which will be used when you connect a slave agent.

If you are only using SSH slaves, then you do NOT need to put that port mapping.

Passing JVM parameters

You might need to customize the JVM running Jenkins, typically to pass system properties (list of props) or tweak heap memory settings. Use JAVA_OPTS environment variable for this purpose :

docker run --name myjenkins -p 8080:8080 -p 50000:50000 --env JAVA_OPTS=-Dhudson.footerURL= jenkins/jenkins:lts

Configuring logging

Jenkins logging can be configured through a properties file and java.util.logging.config.file Java property. For example:

mkdir data
cat > data/ <<EOF
docker run --name myjenkins -p 8080:8080 -p 50000:50000 --env JAVA_OPTS="-Djava.util.logging.config.file=/var/jenkins_home/" -v `pwd`/data:/var/jenkins_home jenkins/jenkins:lts

Configuring reverse proxy

If you want to install Jenkins behind a reverse proxy with prefix, example:, you need to add environment variable JENKINS_OPTS="--prefix=/jenkins" and then follow the below procedures to configure your reverse proxy, which will depend if you have Apache or Nginx:

Passing Jenkins launcher parameters

Argument you pass to docker running the jenkins image are passed to jenkins launcher, so you can run for sample:

docker run jenkins/jenkins:lts --version

This will dump Jenkins version, just like when you run jenkins as an executable war.

You also can define jenkins arguments as JENKINS_OPTS. This is usefull to define a set of arguments to pass to jenkins launcher as you define a derived jenkins image based on the official one with some customized settings. The following sample Dockerfile uses this option to force use of HTTPS with a certificate included in the image

FROM jenkins/jenkins:lts

COPY https.pem /var/lib/jenkins/cert
COPY https.key /var/lib/jenkins/pk
ENV JENKINS_OPTS --httpPort=-1 --httpsPort=8083 --httpsCertificate=/var/lib/jenkins/cert --httpsPrivateKey=/var/lib/jenkins/pk

You can also change the default slave agent port for jenkins by defining JENKINS_SLAVE_AGENT_PORT in a sample Dockerfile.

FROM jenkins/jenkins:lts

or as a parameter to docker,

docker run --name myjenkins -p 8080:8080 -p 50001:50001 --env JENKINS_SLAVE_AGENT_PORT=50001 jenkins/jenkins:lts

Note: This environment variable will be used to set the port adding the system property jenkins.model.Jenkins.slaveAgentPort to JAVA_OPTS.

If this property is already set in JAVA_OPTS, then the value of JENKINS_SLAVE_AGENT_PORT will be ignored.

Installing more tools

You can run your container as root - and install via apt-get, install as part of build steps via jenkins tool installers, or you can create your own Dockerfile to customise, for example:

FROM jenkins/jenkins:lts
# if we want to install via apt
USER root
RUN apt-get update && apt-get install -y ruby make more-thing-here
# drop back to the regular jenkins user - good practice
USER jenkins

In such a derived image, you can customize your jenkins instance with hook scripts or additional plugins. For this purpose, use /usr/share/jenkins/ref as a place to define the default JENKINS_HOME content you wish the target installation to look like :

FROM jenkins/jenkins:lts
COPY custom.groovy /usr/share/jenkins/ref/init.groovy.d/custom.groovy

Preinstalling plugins

You can rely on the script to pass a set of plugins to download with their dependencies. This script will perform downloads from update centers, and internet access is required for the default update centers.

Setting update centers

During the download, the script will use update centers defined by the following environment variables:

It is possible to override the environment variables in images.

❗️ Note that changing this variables will not change the Update Center being used by Jenkins runtime.

Plugin version format

Use plugin artifact ID, without -plugin extension, and append the version if needed separated by :. Dependencies that are already included in the Jenkins war will only be downloaded if their required version is newer than the one included.

There are also custom version specifiers:

  • latest - download the latest version from the main update center. For Jenkins LTS images (example: git:latest)
  • experimental - download the latest version from the experimental update center defined by the JENKINS_UC_EXPERIMENTAL environment variable (example: filesystem_scm:experimental)
  • incrementals;org.jenkins-ci.plugins.workflow;2.19-rc289.d09828a05a74[;githubUserId][;branchName]
  • download the plugin from the Incrementals repo.
    • For this option you need to specify groupId of the plugin. Note that this value may change between plugin versions without notice.
    • In order to automatically update Incrementals in plugins.txt, it is possible to use the Incrementals Maven Plugin: mvn incrementals:updatePluginsTxt -DpluginsFile=plugins.txt. More Info

Fine-tune the downloads

The script uses curl to download the plugins. You can configure the options with some environment variables:

  • CURL_OPTIONS: When downloading the plugins with curl. Curl options. Default value: -sSfL
  • CURL_CONNECTION_TIMEOUT: When downloading the plugins with curl. Maximum time allowed for connection. Default value: 20
  • CURL_RETRY: When downloading the plugins with curl. Retry request if transient problems occur. Default value: 3
  • CURL_RETRY_DELAY: When downloading the plugins with curl. Wait time between retries. Default value: 0
  • CURL_RETRY_MAX_TIME: When downloading the plugins with curl. Retry only within this period. Default value: 60

Other environment variables

In case you have changed some default paths in the image, you can modify their values with these environment variables:

  • REF: directory with preinstalled plugins. Default value: /usr/share/jenkins/ref/plugins
  • JENKINS_WAR: full path to the jenkins.war. Default value: /usr/share/jenkins/jenkins.war

Script usage

You can run the script manually in Dockerfile:

FROM jenkins/jenkins:lts
RUN /usr/local/bin/ docker-slaves github-branch-source:1.8

Furthermore it is possible to pass a file that contains this set of plugins (with or without line breaks).

FROM jenkins/jenkins:lts
COPY plugins.txt /usr/share/jenkins/ref/plugins.txt
RUN /usr/local/bin/ < /usr/share/jenkins/ref/plugins.txt

When jenkins container starts, it will check JENKINS_HOME has this reference content, and copy them there if required. It will not override such files, so if you upgraded some plugins from UI they won't be reverted on next start.

In case you do want to override, append '.override' to the name of the reference file. E.g. a file named /usr/share/jenkins/ref/config.xml.override will overwrite an existing config.xml file in JENKINS_HOME.

Also see JENKINS-24986

Here is an example to get the list of plugins from an existing server:
curl -sSL "http://$JENKINS_HOST/pluginManager/api/xml?depth=1&xpath=/*/*/shortName|/*/*/version&wrapper=plugins" | perl -pe 's/.*?<shortName>([\w-]+).*?<version>([^<]+)()(<\/\w+>)+/\1 \2\n/g'|sed 's/ /:/'

Example Output:


For 2.x-derived images, you may also want to

RUN echo 2.0 > /usr/share/jenkins/ref/jenkins.install.UpgradeWizard.state

to indicate that this Jenkins installation is fully configured. Otherwise a banner will appear prompting the user to install additional plugins, which may be inappropriate.


All the data needed is in the /var/jenkins_home directory - so depending on how you manage that - depends on how you upgrade. Generally - you can copy it out - and then "docker pull" the image again - and you will have the latest LTS - you can then start up with -v pointing to that data (/var/jenkins_home) and everything will be as you left it.

As always - please ensure that you know how to drive docker - especially volume handling!

Upgrading plugins

By default, plugins will be upgraded if they haven't been upgraded manually and if the version from the docker image is newer than the version in the container. Versions installed by the docker image are tracked through a marker file.

To force upgrades of plugins that have been manually upgraded, run the docker image with -e PLUGINS_FORCE_UPGRADE=true.

The default behaviour when upgrading from a docker image that didn't write marker files is to leave existing plugins in place. If you want to upgrade existing plugins without marker you may run the docker image with -e TRY_UPGRADE_IF_NO_MARKER=true. Then plugins will be upgraded if the version provided by the docker image is newer.


If you wish to contribute fixes to this repository, please refer to the dedicated documentation.


Jump on and the #jenkins room. Ask!

You can’t perform that action at this time.