public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
bitnami-containers/bitnami/jenkins
History
…
..
2/debian-12
…
README.md
…
docker-compose.yml
…

README.md

Bitnami Secure Image for Jenkins

What is Jenkins?

Jenkins is an open source Continuous Integration and Continuous Delivery (CI/CD) server designed to automate the building, testing, and deploying of any software project.

Overview of Jenkins Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

docker run --name jenkins bitnami/jenkins:latest

You can find the default credentials and available configuration options in the Environment Variables section.

⚠️ Important Notice: Upcoming changes to the Bitnami Catalog

Beginning August 28th, 2025, Bitnami will evolve its public catalog to offer a curated set of hardened, security-focused images under the new Bitnami Secure Images initiative. As part of this transition:

  • Granting community users access for the first time to security-optimized versions of popular container images.
  • Bitnami will begin deprecating support for non-hardened, Debian-based software images in its free tier and will gradually remove non-latest tags from the public catalog. As a result, community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes
  • Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates.
  • For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images, which include hardened containers, smaller attack surfaces, CVE transparency (via VEX/KEV), SBOMs, and enterprise support.

These changes aim to improve the security posture of all Bitnami users by promoting best practices for software supply chain integrity and up-to-date deployments. For more details, visit the Bitnami Secure Images announcement.

Why use Bitnami Secure Images?

  • Bitnami Secure Images and Helm charts are built to make open source more secure and enterprise ready.
  • Triage security vulnerabilities faster, with transparency into CVE risks using industry standard Vulnerability Exploitability Exchange (VEX), KEV, and EPSS scores.
  • Our hardened images use a minimal OS (Photon Linux), which reduces the attack surface while maintaining extensibility through the use of an industry standard package format.
  • Stay more secure and compliant with continuously built images updated within hours of upstream patches.
  • 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.
  • Hardened images come with attestation signatures (Notation), SBOMs, virus scan reports and other metadata produced in an SLSA-3 compliant software factory.

Only a subset of BSI applications are available for free. Looking to access the entire catalog of applications as well as enterprise support? Try the commercial edition of Bitnami Secure Images today.

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.

Why use a non-root container?

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.

Supported tags and respective Dockerfile links

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

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

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

Get this image

The recommended way to get the Bitnami Jenkins Docker Image is to pull the prebuilt image from the Docker Hub Registry.

docker pull bitnami/jenkins:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

docker pull bitnami/jenkins:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .

How to use this image

Using the Docker Command Line

Step 1: Create a network

docker network create jenkins-network

Step 2: Create volumes for Jenkins persistence and launch the container

$ docker volume create --name jenkins_data
docker run -d -p 80:8080 --name jenkins \
  --network jenkins-network \
  --volume jenkins_data:/bitnami/jenkins \
  bitnami/jenkins:latest

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/jenkins 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

This requires a minor change to the docker-compose.yml file present in this repository:

  ...
  services:
    jenkins:
    ...
    volumes:
-     - jenkins_data:/bitnami/jenkins
+     - /path/to/jenkins-persistence:/bitnami/jenkins
- volumes:
-   jenkins_data:
-     driver: local

NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Mount host directories as data volumes using the Docker command line

Step 1: Create a network (if it does not exist)

docker network create jenkins-network

Step 2. Create the Jenkins container with host volumes

docker run -d -p 80:8080 --name jenkins \
  --network jenkins-network \
  --volume /path/to/jenkins-persistence:/bitnami/jenkins \
  bitnami/jenkins:latest

Using Docker Compose

curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/jenkins/docker-compose.yml > docker-compose.yml
docker-compose up -d

Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated Bitnami Helm chart.

If you detect any issue in the docker-compose.yaml file, feel free to report it or contribute with a fix by following our Contributing Guidelines.

Configuration

Environment variables

Customizable environment variables

Name Description Default Value
JENKINS_HOME Jenkins home directory. ${JENKINS_VOLUME_DIR}/home
JENKINS_PLUGINS Comma-separated list of Jenkins plugins to be installed. nil
JENKINS_PLUGINS_LATEST Set to false to install the minimum required version. true
JENKINS_PLUGINS_LATEST_SPECIFIED Set to true to install the latest dependencies of any plugin that is requested to have the latest version. false
JENKINS_SKIP_IMAGE_PLUGINS Set to true to skip the installation of image built-in plugins. false
JENKINS_OVERRIDE_PLUGINS Set to true to force overriding existing plugins from the persisted volume. false
JENKINS_OVERRIDE_PATHS Comma-separated list of relative paths to be removed from the Jenkins home and recreated if present in the mounted content directory. nil
JENKINS_HTTP_LISTEN_ADDRESS Jenkins HTTP listen address. nil
JENKINS_HTTPS_LISTEN_ADDRESS Jenkins HTTPS listen address. nil
JENKINS_HTTP_PORT_NUMBER Jenkins HTTP port number. nil
JENKINS_HTTPS_PORT_NUMBER Jenkins HTTPS port number. nil
JENKINS_JNLP_PORT_NUMBER Jenkins JNLP port number. nil
JENKINS_EXTERNAL_HTTP_PORT_NUMBER Port to access Jenkins from outside of the instance using HTTP. 80
JENKINS_EXTERNAL_HTTPS_PORT_NUMBER Port to access Jenkins from outside of the instance using HTTPS. 443
JENKINS_HOST Jenkins hostname. nil
JENKINS_FORCE_HTTPS Enable serving Jenkins through HTTPS instead of HTTP. no
JENKINS_SKIP_BOOTSTRAP Whether to perform initial bootstrapping for the application. no
JENKINS_ENABLE_SWARM Enable the Jenkins Swarm configuration. no
JENKINS_CERTS_DIR Password of keystore. ${JENKINS_HOME}
JENKINS_KEYSTORE_PASSWORD Password of keystore. bitnami
JENKINS_OPTS Jenkins launcher parameters. nil
JENKINS_USERNAME Jenkins admin user name. user
JENKINS_PASSWORD Jenkins admin user password. bitnami
JENKINS_EMAIL Jenkins admin user e-mail address. user@example.com
JENKINS_SWARM_USERNAME Jenkins user for Swarm access name . swarm
JENKINS_SWARM_PASSWORD Jenkins user for Swarm access password. nil
JAVA_HOME Java Home directory. ${BITNAMI_ROOT_DIR}/java
JAVA_OPTS Java options. nil

Read-only environment variables

Name Description Value
JENKINS_BASE_DIR Jenkins installation directory. ${BITNAMI_ROOT_DIR}/jenkins
JENKINS_LOGS_DIR Jenkins directory for log files. ${JENKINS_BASE_DIR}/logs
JENKINS_LOG_FILE Path to the Jenkins log file. ${JENKINS_LOGS_DIR}/jenkins.log
JENKINS_TMP_DIR Jenkins directory for runtime temporary files. ${JENKINS_BASE_DIR}/tmp
JENKINS_PID_FILE Path to the Jenkins PID file. ${JENKINS_TMP_DIR}/jenkins.pid
JENKINS_TEMPLATES_DIR Path to the directory containing templates to generate groovy scripts. ${BITNAMI_ROOT_DIR}/scripts/jenkins/bitnami-templates
JENKINS_VOLUME_DIR Persistence base directory. ${BITNAMI_VOLUME_DIR}/jenkins
JENKINS_MOUNTED_CONTENT_DIR Directory to mount custom Jenkins content (such as Groovy scripts or configuration files). /usr/share/jenkins/ref
JENKINS_DAEMON_USER Jenkins system user. jenkins
JENKINS_DAEMON_GROUP Jenkins system group. jenkins
JENKINS_DEFAULT_HTTP_LISTEN_ADDRESS Default Jenkins HTTP listen address to enable at build time. 0.0.0.0
JENKINS_DEFAULT_HTTPS_LISTEN_ADDRESS Default Jenkins HTTPS listen address to enable at build time. 0.0.0.0
JENKINS_DEFAULT_HTTP_PORT_NUMBER Default Jenkins HTTP port number to enable at build time. 8080
JENKINS_DEFAULT_HTTPS_PORT_NUMBER Default Jenkins HTTPS port number to enable at build time. 8443
JENKINS_DEFAULT_JNLP_PORT_NUMBER Default Jenkins JNLP port number to enable at build time. 50000

When you start the Jenkins image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. If you want to add a new environment variable:

  • For docker-compose add the variable name and value under the application section in the docker-compose.yml file present in this repository:

    jenkins:
  ...
  environment:
    - JENKINS_PASSWORD=my_password
  ...

  • For manual execution add a --env option with each variable and value:

    $ docker run -d -p 80:8080 --name jenkins \
  --env JENKINS_PASSWORD=my_password \
  --network jenkins-network \
  --volume /path/to/jenkins-persistence:/bitnami/jenkins \
  bitnami/jenkins:latest

FIPS configuration in Bitnami Secure Images

The Bitnami Jenkins Docker image from the Bitnami Secure Images catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:

  • OPENSSL_FIPS: whether OpenSSL runs in FIPS mode or not. yes (default), no.

Logging

The Bitnami Jenkins Docker image sends the container logs to stdout. To view the logs:

docker logs jenkins

Or using Docker Compose:

docker-compose logs jenkins

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

Maintenance

Backing up your container

To backup your data, configuration and logs, follow these simple steps:

Step 1: Stop the currently running container

  • For docker-compose: $ docker-compose stop jenkins
  • For manual execution: $ docker stop jenkins

Step 2: Run the backup command

We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.

docker run --rm -v /path/to/jenkins-backups:/backups --volumes-from jenkins bitnami/os-shell \
  cp -a /bitnami/jenkins /backups/latest

Restoring a backup

Restoring a backup is as simple as mounting the backup as volumes in the containers.

 $ docker run -d --name jenkins \
   ...
-  --volume /path/to/jenkins-persistence:/bitnami/jenkins \
+  --volume /path/to/jenkins-backups/latest:/bitnami/jenkins \
   bitnami/jenkins:latest

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.

Step 1. Get the updated images

docker pull bitnami/jenkins:latest

Step 2. Stop your container

  • For docker-compose: $ docker-compose stop jenkins
  • For manual execution: $ docker stop jenkins

Step 3. Take a snapshot of the application state

Follow the steps in Backing up your container to take a snapshot of the current application state.

Step 4. Remove the stopped container

  • For docker-compose: $ docker-compose rm -v jenkins
  • For manual execution: $ docker rm -v jenkins

Step 5. 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

Customize this image

For customizations, please note that this image is, by default, a non-root container using the user jenkins with uid=1001.

Extend this image

To extend the bitnami original image, you can create your own image using a Dockerfile with the format below:

FROM bitnami/jenkins
## Put your customizations below
...

Here is an example of extending the image with the following modifications:

  • Install the vim editor
FROM bitnami/jenkins

## Change user to perform privileged actions
USER 0
## Install 'vim'
RUN install_packages vim
## Revert to the original non-root user
USER 1001

Installing plugins

To download and install a set of plugins and their dependencies, use the Plugin Installation Manager tool. You can find information about how to use this tool in the guide below:

Alternatively, it is possible to install plugins using the following env variables:

  • JENKINS_PLUGINS: Comma-separated list of Jenkins plugins to be installed during the first boot.
  • JENKINS_PLUGINS_LATEST: If set to false, install the minimum required version of the plugins in JENKINS_PLUGINS. Default: true
  • JENKINS_PLUGINS_LATEST_SPECIFIED: If set to true, install the latest dependencies of any plugin that is requested to have the latest version. Default: false
  • JENKINS_OVERRIDE_PLUGINS: If set to true, existing plugins in the persisted volume will be removed and will force plugins to be reinstalled. Default: false
  • JENKINS_SKIP_IMAGE_PLUGINS: If set to true, skip the installation of image built-in plugins. Default: false

Passing JVM parameters

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

docker run -d --name jenkins -p 80:8080 \
  --env JAVA_OPTS=-Dhudson.footerURL=http://mycompany.com \
  bitnami/jenkins:latest

Using custom launcher parameters

In order to use custom parameters for Jenkins launcher, for example if you need to install Jenkins behind a reverse proxy with a prefix such as mycompany.com/jenkins, you can use the "JENKINS_OPTS" environment variable:

docker run -d --name jenkins -p 8080:8080 \
  --env JENKINS_OPTS="--prefix=/jenkins" \
  bitnami/jenkins:latest

Skipping Bitnami initialization

By default, when running this image, Bitnami implement some logic in order to configure it for working out of the box. This initialization consists of creating the user and password, preparing data to persist, configuring permissions, creating the JENKINS_HOME, etc. You can skip it in two ways:

  • Setting the JENKINS_SKIP_BOOTSTRAP environment variable to yes.
  • Attaching a volume with a custom JENKINS_HOME that contains a functional Jenkins installation.

Adding files/directories to the image

You can include files to the image automatically. All files/directories located in /usr/share/jenkins/ref are copied to /bitnami/jenkins/home (default Jenkins home directory).

Examples

Run groovy scripts at Jenkins start up

You can create custom groovy scripts and make Jenkins run them at start up.

However, using this feature will disable the default configuration done by the Bitnami scripts. This is intended to customize the Jenkins configuration by code.

$ mkdir jenkins-init.groovy.d
$ echo "println '--> hello world'" > jenkins-init.groovy.d/AA_hello.groovy
$ echo "println '--> bye world'" > jenkins-init.groovy.d/BA_bye.groovy

docker run -d -p 80:8080 --name jenkins \
  --env "JENKINS_SKIP_BOOTSTRAP=yes" \
  --volume "$(pwd)/jenkins-init.groovy.d:/usr/share/jenkins/ref/init.groovy.d" \
  bitnami/jenkins:latest

$ docker logs jenkins | grep world
--> hello world!
--> bye world!
Run custom config.xml

You can use your our own config.xml file. However, using this feature will disable the default configuration generated by the Bitnami scripts. This is intended to customize the Jenkins configuration by code.

docker run -d -p 80:8080 --name jenkins \
  --env "JENKINS_SKIP_BOOTSTRAP=yes" \
  --volume "$(pwd)/config.xml:/usr/share/jenkins/ref/config.xml" \
  bitnami/jenkins:latest

NOTE: The default admin user with this setup will not be created. It should be done separately.

Notable Changes

2.346.3-debian-11-r3

  • The preinstalled plugins were removed.

2.332.2-debian-10-r21

  • HTTPS and HTTP support are enabled by default.
  • JENKINS_ENABLE_HTTPS has been renamed to JENKINS_FORCE_HTTPS.

2.277.4-debian-10-r19

  • The size of the container image has been decreased.
  • The configuration logic is now based on Bash scripts in the rootfs/ folder.
  • Only the Jenkins Home directory is persisted.
  • The install-plugins.sh script has been deprecated. Instead use the Plugin Installation Manager Tool as explained in the Installing Plugins section.
  • The DISABLE_JENKINS_INITIALIZATION environment variable was renamed to JENKINS_SKIP_BOOTSTRAP.

2.263.3-debian-10-rXX

2.222.1-debian-10-r17

  • Java distribution has been migrated from AdoptOpenJDK to OpenJDK Liberica. As part of VMware, we have an agreement with Bell Software to distribute the Liberica distribution of OpenJDK. That way, we can provide support & the latest versions and security releases for Java.

2.204.4-debian-10-r3

  • The Jenkins container has been migrated to a "non-root" user approach. Previously the container ran as the root user and the Jenkins service was started as the jenkins user. From now on, both the container and the Jenkins service run as user jenkins (uid=1001). You can revert this behavior by changing USER 1001 to USER root in the Dockerfile.
  • Consequences:
    • Backwards compatibility is not guaranteed when data is persisted using docker or docker-compose. We highly recommend migrating your Jenkins data ensuring the jenkins user has the appropriate permissions.
    • No "privileged" actions are allowed anymore.

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

  • Use Jetty instead of Tomcat as web server.

2.107.1-r0

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

Contributing

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

Issues

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to fill the issue template.

License

Copyright © 2025 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

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

http://www.apache.org/licenses/LICENSE-2.0

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.