Bitnami Docker Image for Jenkins
Switch branches/tags
2.138.1-ol-7-r8 2.138.1-ol-7-r7 2.138.1-ol-7-r6 2.138.1-ol-7-r5 2.138.1-ol-7-r4 2.138.1-ol-7-r3 2.138.1-ol-7-r2 2.138.1-ol-7-r1 2.138.1-ol-7-r0 2.138.1-debian-9-r6 2.138.1-debian-9-r5 2.138.1-debian-9-r4 2.138.1-debian-9-r3 2.138.1-debian-9-r2 2.138.1-debian-9-r1 2.138.1-debian-9-r0 2.121.3-ol-7-r22 2.121.3-ol-7-r21 2.121.3-ol-7-r20 2.121.3-ol-7-r19 2.121.3-ol-7-r18 2.121.3-ol-7-r17 2.121.3-ol-7-r16 2.121.3-ol-7-r15 2.121.3-ol-7-r14 2.121.3-ol-7-r13 2.121.3-ol-7-r12 2.121.3-ol-7-r11 2.121.3-ol-7-r10 2.121.3-ol-7-r9 2.121.3-ol-7-r8 2.121.3-ol-7-r7 2.121.3-ol-7-r6 2.121.3-ol-7-r5 2.121.3-ol-7-r4 2.121.3-ol-7-r3 2.121.3-ol-7-r2 2.121.3-ol-7-r1 2.121.3-ol-7-r0 2.121.3-debian-9-r15 2.121.3-debian-9-r14 2.121.3-debian-9-r13 2.121.3-debian-9-r12 2.121.3-debian-9-r11 2.121.3-debian-9-r10 2.121.3-debian-9-r9 2.121.3-debian-9-r8 2.121.3-debian-9-r7 2.121.3-debian-9-r6 2.121.3-debian-9-r5 2.121.3-debian-9-r4 2.121.3-debian-9-r3 2.121.3-debian-9-r2 2.121.3-debian-9-r1 2.121.3-debian-9-r0 2.121.2-ol-7-r23 2.121.2-ol-7-r22 2.121.2-ol-7-r21 2.121.2-ol-7-r20 2.121.2-ol-7-r19 2.121.2-ol-7-r18 2.121.2-ol-7-r17 2.121.2-ol-7-r16 2.121.2-ol-7-r15 2.121.2-ol-7-r14 2.121.2-ol-7-r13 2.121.2-ol-7-r12 2.121.2-ol-7-r11 2.121.2-ol-7-r10 2.121.2-ol-7-r9 2.121.2-ol-7-r8 2.121.2-ol-7-r7 2.121.2-ol-7-r6 2.121.2-ol-7-r5 2.121.2-ol-7-r4 2.121.2-ol-7-r3 2.121.2-ol-7-r2 2.121.2-ol-7-r1 2.121.2-ol-7-r0 2.121.2-debian-9-r27 2.121.2-debian-9-r26 2.121.2-debian-9-r25 2.121.2-debian-9-r24 2.121.2-debian-9-r23 2.121.2-debian-9-r22 2.121.2-debian-9-r21 2.121.2-debian-9-r20 2.121.2-debian-9-r19 2.121.2-debian-9-r18 2.121.2-debian-9-r17 2.121.2-debian-9-r16 2.121.2-debian-9-r15 2.121.2-debian-9-r14 2.121.2-debian-9-r13 2.121.2-debian-9-r12 2.121.2-debian-9-r11 2.121.2-debian-9-r10 2.121.2-debian-9-r9 2.121.2-debian-9-r8 2.121.2-debian-9-r7
Nothing to show
Clone or download
carrodher Merge pull request #49 from bitnami/remove_debian_8
Removed Debian 8 from root version folders
Latest commit 1f6b272 Sep 21, 2018


What is Jenkins?

Jenkins is widely recognized as the most feature-rich CI available with easy configuration, continuous delivery and continuous integration support, easily test, build and stage your app, and more. It supports multiple SCM tools including CVS, Subversion and Git. It can execute Apache Ant and Apache Maven-based projects as well as arbitrary scripts.


Docker Compose

$ curl -sSL > docker-compose.yml
$ docker-compose up -d

Why use Bitnami Images?

  • Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
  • With Bitnami images the latest bug fixes and features are available as soon as possible.
  • Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
  • Bitnami images are built on CircleCI and automatically pushed to the Docker Hub.
  • All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.

How to deploy Jenkins in Kubernetes?

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Jenkins Chart GitHub repository.

Supported tags and respective Dockerfile links

NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

Subscribe to project updates by watching the bitnami/jenkins GitHub repo.


To run this application you need Docker Engine >= 1.10.0. Docker Compose is recommended with a version 1.6.0 or later.

How to use this image

Using Docker Compose

The recommended way to run Jenkins is using Docker Compose using the following docker-compose.yml template:

version: '2'
    image: 'bitnami/jenkins:latest'
      - '80:8080'
      - '443:8443'
      - 'jenkins_data:/bitnami'
    driver: local

Launch the containers using:

$ docker-compose up -d

Using the Docker Command Line

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

  1. Create a network
$ docker network create jenkins-tier
  1. Create volumes for Jenkins persistence and launch the container
$ docker volume create --name jenkins_data
$ docker run -d --name jenkins -p 80:8080 -p 443:8443 \
  --net jenkins-tier \
  --volume jenkins_data:/bitnami \

Access your application at http://your-ip/

Persisting your application

If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a volume at the /bitnami path. The above examples define a docker volume namely jenkins_data. The Jenkins application state will persist as long as this volume is not removed.

To avoid inadvertent removal of this volume you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

Mount host directories as data volumes with Docker Compose

The following docker-compose.yml template demonstrates the use of host directories as data volumes.

version: '2'

    image: bitnami/jenkins:latest
      - '80:8080'
      - '443:8443'
      - /path/to/jenkins-persistence:/bitnami

Mount host directories as data volumes using the Docker command line

  1. Create a network (if it does not exist)
$ docker network create jenkins-tier
  1. Create the Jenkins the container with host volumes
$ docker run -d --name jenkins -p 80:8080 -p 443:8443 \
  --net jenkins-tier \
  --volume /path/to/jenkins-persistence:/bitnami \

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, an internet access is required for the default update centers.

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.

A custom version specifier can also be used:

  • latest - download the latest version from the main update center. For Jenkins LTS images (example: git:latest)

Script usage

You can run the script manually in Dockerfile adding the following sentence after COPY rootfs /:

RUN / 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), you should locate this file in the rootfs directory.

RUN / < /plugins.txt

Upgrading Jenkins

Bitnami provides up-to-date versions of Jenkins, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the Jenkins container.

  1. Get the updated images:
$ docker pull bitnami/jenkins:latest
  1. Stop your container
  • For docker-compose: $ docker-compose stop jenkins
  • For manual execution: $ docker stop jenkins
  1. Take a snapshot of the application state
$ rsync -a /path/to/jenkins-persistence /path/to/jenkins-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

You can use this snapshot to restore the application state should the upgrade fail.

  1. Remove the stopped container
  • For docker-compose: $ docker-compose rm -v jenkins
  • For manual execution: $ docker rm -v jenkins
  1. Run the new image
  • For docker-compose: $ docker-compose up jenkins
  • For manual execution (mount the directories if needed): docker run --name jenkins bitnami/jenkins:latest


Environment variables

The Jenkins instance can be customized by specifying environment variables on the first run. The following environment values are provided to custom Jenkins:

  • JENKINS_USERNAME: Jenkins admin username. Default: user
  • JENKINS_PASSWORD: Jenkins admin password. Default: bitnami

Specifying Environment variables using Docker Compose

version: '2'

    image: bitnami/jenkins:latest
      - '80:8080'
      - '443:8443'
      - JENKINS_PASSWORD=my_password
      - jenkins_data:/bitnami

    driver: local

Specifying Environment variables on the Docker command line

$ docker run -d --name jenkins -p 80:8080 -p 443:8443 \
  --net jenkins-tier \
  --env JENKINS_PASSWORD=my_password \
  --volume jenkins_data:/bitnami \

Notable Changes

2.121.2-ol-7-r14 / 2.121.2-debian-9-r18

  • Use Jetty instead of Tomcat as web server.


  • The Jenkins container has been migrated to the LTS version. From now on, this repository will only track long term support releases from Jenkins.


We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.


If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

  • Host OS and version
  • Docker version (docker version)
  • Output of docker info
  • Version of this container (echo $BITNAMI_IMAGE_VERSION inside the container)
  • The command you used to run the container, and any relevant output you saw (masking any sensitive information)


Copyright 2015-2018 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.