bitnami/jmx-exporter

Bitnami Secure Image for JMX Exporter

A process for exposing JMX Beans via HTTP for Prometheus consumption.

https://github.com/prometheus/jmx_exporter 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

console
docker run --name jmx-exporter REGISTRY_NAME/bitnami/jmx-exporter:latest

Note: You need to substitute the REGISTRY_NAME placeholder with a reference to your container registry.

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.

Get this image

The recommended way to get the Bitnami JMX Exporter Docker Image is to pull the prebuilt image from the https://hub.docker.com/r/bitnami/jmx-exporter.

console
docker pull REGISTRY_NAME/bitnami/jmx-exporter:latest

To use a specific version, you can pull a versioned tag. You can view the https://hub.docker.com/r/bitnami/jmx-exporter/tags/ in the Docker Hub Registry.

console
docker pull REGISTRY_NAME/bitnami/jmx-exporter:[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.

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

Connecting to other containers

Using Docker container networking, a different server running inside a container can easily be accessed by your application containers and vice-versa.

Containers attached to the same network can communicate with each other using the container name as the hostname.

Using the Command Line

Step 1: Create a network

console
docker network create jmx-exporter-network --driver bridge

Step 2: Launch the jmx-exporter container within your network

Use the --network <NETWORK> argument to the docker run command to attach the container to the jmx-exporter-network network.

console
docker run --name jmx-exporter-node1 --network jmx-exporter-network REGISTRY_NAME/bitnami/jmx-exporter:latest

Step 3: Run another containers

We can launch another containers using the same flag (--network NETWORK) in the docker run command. If you also set a name to your container, you will be able to use it as hostname in your network.

Configuration

Find all the configuration options in the https://github.com/prometheus/jmx_exporter#configuration.

FIPS configuration in Bitnami Secure Images

The Bitnami JMX Exporter 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.
• JAVA_TOOL_OPTIONS: controls Java FIPS mode. Use -Djava.security.properties==/opt/bitnami/java/conf/security/java.security.restricted (restricted), -Djava.security.properties==/opt/bitnami/java/conf/security/java.security.relaxed (relaxed), or -Djava.security.properties==/opt/bitnami/java/conf/security/java.security.original (off).

Logging

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

console
docker logs jmx-exporter

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.

Notable Changes

Starting January 16, 2024

• The docker-compose.yaml file has been removed, as it was solely intended for internal testing purposes.

License

Copyright © 2026 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

<[***]>

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.