98a68440f2
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com> |
||
|---|---|---|
| .. | ||
| 1 | ||
| 2/debian-12 | ||
| README.md | ||
| docker-compose.yml | ||
README.md
Bitnami Secure Image for Jaeger
What is Jaeger?
Jaeger is a distributed tracing system. It is used for monitoring and troubleshooting microservices-based distributed systems.
Overview of Jaeger 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 jaeger bitnami/jaeger:latest
Why use Bitnami Secure Images?
Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise OS Photon Linux. Why choose BSI images?
- Hardened secure images of popular open source software with Near-Zero Vulnerabilities
- Vulnerability Triage & Prioritization with VEX Statements, KEV and EPSS Scores
- Compliance focus with FIPS, STIG, and air-gap options, including secure bill of materials (SBOM)
- Software supply chain provenance attestation through in-toto
- First class support for the internet’s favorite Helm charts
Each image comes with valuable security metadata. You can view the metadata in our public catalog here. Note: Some data is only available with commercial subscriptions to BSI.
If you are looking for our previous generation of images based on Debian Linux, please see the Bitnami Legacy registry.
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 Jaeger Docker Image is to pull the prebuilt image from the Docker Hub Registry.
docker pull bitnami/jaeger: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/jaeger:[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 .
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.
Configuration
Environment variables
Customizable environment variables
| Name | Description | Default Value |
|---|---|---|
JAEGER_USERNAME |
Jaeger username. | user |
JAEGER_PASSWORD |
Jaeger password. | bitnami |
JAEGER_AGENT_ZIPKIN_UDP_PORT_NUMBER |
Jaeger Agent UDP port. Accept zipkin.thrift over compact thrift protocol | 5775 |
JAEGER_AGENT_COMPACT_UDP_PORT_NUMBER |
Jaeger Agent UDP port. Accept jaeger.thrift over compact thrift protocol | 6831 |
JAEGER_AGENT_BINARY_UDP_PORT_NUMBER |
Jaeger Agent UDP port. Accept jaeger.thrift over binary thrift protocol | 6832 |
JAEGER_AGENT_HTTP_PORT_NUMBER |
Jaeger Agent HTTP port. Serve configs. | 5778 |
JAEGER_QUERY_HTTP_PORT_NUMBER |
Jaeger Query HTTP port. | 16686 |
JAEGER_QUERY_GRPC_PORT_NUMBER |
Jaeger Query GRPC port. | 16685 |
JAEGER_COLLECTOR_ZIPKIN_PORT_NUMBER |
Jaeger Collector Zipkin compatible port. | nil |
JAEGER_COLLECTOR_HTTP_PORT_NUMBER |
Jaeger Collector HTTP port. Accept jaeger.thrift directly from clients | 14268 |
JAEGER_COLLECTOR_GRPC_PORT_NUMBER |
Jaeger Collector GRPC port. Accept jaeger.thrift directly from clients | 14250 |
JAEGER_ADMIN_HTTP_PORT_NUMBER |
Jaeger Admin port. | 14269 |
JAEGER_METRICS_PORT_NUMBER |
Jaeger prometheus metrics port. | 8888 |
JAEGER_HEALTHCHECK_PORT_NUMBER |
Jaeger healthcheck port. | 13133 |
JAEGER_COLLECTOR_OTLP_GRPC_PORT_NUMBER |
Jaeger Collector OpenTelemetry gRPC port. | 4317 |
JAEGER_COLLECTOR_OTLP_HTTP_PORT_NUMBER |
Jaeger Collector OpenTelemetry HTTP port. | 4318 |
JAEGER_AGENT_ZIPKIN_UDP_HOST |
Jaeger Agent UDP host. Accept zipkin.thrift over compact thrift protocol | 0.0.0.0 |
JAEGER_AGENT_COMPACT_UDP_HOST |
Jaeger Agent UDP host. Accept jaeger.thrift over compact thrift protocol | 0.0.0.0 |
JAEGER_AGENT_BINARY_UDP_HOST |
Jaeger Agent UDP host. Accept jaeger.thrift over binary thrift protocol | 0.0.0.0 |
JAEGER_AGENT_HTTP_HOST |
Jaeger Agent HTTP host. Serve configs. | 0.0.0.0 |
JAEGER_QUERY_HTTP_HOST |
Jaeger Query HTTP host. | 0.0.0.0 |
JAEGER_QUERY_GRPC_HOST |
Jaeger Query GRPC host. | 0.0.0.0 |
JAEGER_COLLECTOR_HTTP_HOST |
Jaeger Collector Zipkin compatible host. | 0.0.0.0 |
JAEGER_COLLECTOR_GRPC_HOST |
Jaeger Collector HTTP host. Accept jaeger.thrift directly from clients | 0.0.0.0 |
JAEGER_ADMIN_HTTP_HOST |
Jaeger Collector GRPC host. Accept jaeger.thrift directly from clients | 0.0.0.0 |
JAEGER_COLLECTOR_ZIPKIN_HOST |
Jaeger Admin host. | 0.0.0.0 |
JAEGER_METRICS_HOST |
Jaeger prometheus metrics host. | 0.0.0.0 |
JAEGER_HEALTHCHECK_HOST |
Jaeger healthcheck host. | 0.0.0.0 |
JAEGER_COLLECTOR_OTLP_GRPC_HOST |
Jaeger Collector OpenTelemetry gRPC host. | 0.0.0.0 |
JAEGER_COLLECTOR_OTLP_HTTP_HOST |
Jaeger Collector OpenTelemetry HTTP host. | 0.0.0.0 |
JAEGER_APACHE_QUERY_HTTP_PORT_NUMBER |
Jaeger Query UI HTTP port, exposed via Apache with basic authentication. | nil |
JAEGER_APACHE_QUERY_HTTPS_PORT_NUMBER |
Jaeger Query UI HTTPS port, exposed via Apache with basic authentication. | nil |
JAEGER_APACHE_COLLECTOR_HTTP_PORT_NUMBER |
Jaeger Collector HTTP port, exposed via Apache with basic authentication. | 14270 |
JAEGER_APACHE_COLLECTOR_HTTPS_PORT_NUMBER |
Jaeger Collector HTTPS port, exposed via Apache with basic authentication. | 14271 |
SPAN_STORAGE_TYPE |
Jaeger storage type. | cassandra |
JAEGER_CASSANDRA_HOST |
Cassandra server host. | 127.0.0.1 |
JAEGER_CASSANDRA_PORT_NUMBER |
Cassandra server port. | 9042 |
JAEGER_CASSANDRA_KEYSPACE |
Cassandra keyspace. | bn_jaeger |
JAEGER_CASSANDRA_DATACENTER |
Cassandra keyspace. | dc1 |
JAEGER_CASSANDRA_USER |
Cassandra user name. | cassandra |
JAEGER_CASSANDRA_PASSWORD |
Cassandra user password. | nil |
JAEGER_CASSANDRA_ALLOWED_AUTHENTICATORS |
Comma-separated list of allowed password authenticators for Cassandra. | org.apache.cassandra.auth.PasswordAuthenticator |
Read-only environment variables
| Name | Description | Value |
|---|---|---|
JAEGER_BASE_DIR |
Jaeger installation directory. | ${BITNAMI_ROOT_DIR}/jaeger |
JAEGER_BIN_DIR |
Jaeger directory for binary files. | ${JAEGER_BASE_DIR}/bin |
JAEGER_CONF_DIR |
Jaeger configuration directory. | ${JAEGER_BASE_DIR}/conf |
JAEGER_CONF_FILE |
Jaeger configuration file. | ${JAEGER_CONF_DIR}/jaeger.yml |
JAEGER_LOGS_DIR |
Jaeger logs directory. | ${JAEGER_BASE_DIR}/logs |
JAEGER_LOG_FILE |
Jaeger log file. | ${JAEGER_LOGS_DIR}/jaeger.log |
JAEGER_TMP_DIR |
Jaeger temporary directory. | ${JAEGER_BASE_DIR}/tmp |
JAEGER_PID_FILE |
Jaeger PID file. | ${JAEGER_TMP_DIR}/jaeger.pid |
JAEGER_DAEMON_USER |
Jaeger daemon system user. | jaeger |
JAEGER_DAEMON_GROUP |
Jaeger daemon system group. | jaeger |
Running commands
To run commands inside this container you can use docker run, for example to execute jaeger --help you can follow the example below:
docker run --rm --name jaeger bitnami/jaeger:latest --help
Check the official Jaeger documentation for more information.
FIPS configuration in Bitnami Secure Images
The Bitnami Jaeger 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.
Using docker-compose.yaml
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.
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.