bitnami/thanos
Bitnami container image for Thanos
10M+
Thanos is a highly available metrics system that can be added on top of existing Prometheus deployments, providing a global query view across all Prometheus installations.
Overview of Thanos 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.
docker run --name thanos bitnami/thanos:latest
Looking to use Thanos in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.
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 Thanos Chart GitHub repository.
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.
Starting December 10th 2024, only the latest stable branch of any container will receive updates in the free Bitnami catalog. To access up-to-date releases for all upstream-supported branches, consider upgrading to Bitnami Premium. Previous versions already released will not be deleted. They are still available to pull from DockerHub.
Please check the Bitnami Premium page in our partner Arrow Electronics for more information.
Dockerfile
linksLearn 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.
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.
Step 1: Create a network
docker network create thanos-network --driver bridge
Step 2: Create a volume for Prometheus data
docker volume create --name prometheus_data
Step 3: Launch a Prometheus container within your network
Create a configuration file prometheus.yml for Prometheus as the one below:
global:
scrape_interval: 5s
# mandatory
# used by Thanos Query to filter out store APIs to touch during query requests
external_labels:
foo: bar
scrape_configs:
- job_name: prometheus
static_configs:
- targets:
- localhost:9090
Use the docker run
command to launch the Prometheus containers using the arguments below:
--network <network>
argument to attach the container to the thanos-network
network.--volume [host-src:]container-dest[:<options>]
argument to mount the configuration file for Prometheus and a data volume to avoid loss of data. As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001
.docker run -d --name "prometheus" \
--network "thanos-network" \
--volume "$(pwd)/prometheus.yml:/opt/bitnami/prometheus/conf/prometheus.yml:ro" \
--volume "prometheus_data:/opt/bitnami/prometheus/data" \
bitnami/prometheus
Step 4: Launch a Thanos sidecar container within your network
Use the docker run
command to launch the Thanos sidecar container using the argument below and overwriting the default command:
--network <network>
argument to attach the container to the thanos-network
network.--volume [host-src:]container-dest[:<options>]
argument to mount the Prometheus data volume.docker run -d --name "thanos-sidecar" \
--network "thanos-network" \
--volume "prometheus_data:/data" \
bitnami/thanos sidecar --tsdb.path=/data --prometheus.url=http://prometheus:9090 --grpc-address=0.0.0.0:10901
Step 5: Launch a Thanos Query container within your network
Use the docker run
command to launch the Thanos Query container using the argument below and overwriting the default command:
--network <network>
argument to attach the container to the thanos-network
network.--expose [hostPort:containerPort]
argument to expose the port 9090
.docker run -d --name "thanos-query" \
--network "thanos-network" \
--expose "9090:9090" \
bitnami/thanos query --grpc-address=0.0.0.0:10901 --http-address=0.0.0.0:9090 --store=thanos-sidecar:10901
Then you can access your Thanos Query UI at http://localhost:9090/
You can use the docker-compose-cluster.yml available on this repository to deploy an architecture like the one below:
┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Node │ │ Thanos │───────────▶ │ Thanos Store │ │ Thanos │
│ Exporter │ │ Query │──┐ │ Gateway │ │ Compactor │
└──────────────┘ └──────────────┘ │ └──────────────┘ └──────────────┘
▲ │ │ │
│ gather hardware │ query │ storages │ Compact & downsample
│ & OS metrics │ metrics │ query metrics │ blocks
│ │ │ │
┌ ── ── ── ── ── ── ── ── ── ── ── ──┐ | | |
│┌──────────────┐ ┌──────────────┐│ │ ▼ │
││ Prometheus │ ─▶ │ Thanos ││ ◀─────────────┘ ┌──────────────┐ │
││ │ ◀─ │ Sidecar ││ │ MinIO │◀─────────────┘
│└──────────────┘ └──────────────┘│ │ │
└ ── ── ── ── ── ── ── ── ── ── ── ──┘ └──────────────┘
Under the configuration section you can find more information about each component's role. The unique "mandatory" components are Prometheus, Thanos Sidecar and Thanos Query. The rest of components are optional.
To do so, run the commands below:
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/minio/master/docker-compose-cluster.yml > docker-compose.yml
docker-compose up -d
Thanos can be configured via command-line flags and, depending on them, the same container image can be used to create components with differentes roles:
For further documentation, please check Thanos documentation.
The Bitnami Thanos Docker image sends the container logs to the stdout
. To view the logs:
docker logs thanos
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.
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.
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.
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.
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.