[bitnami/thanos] Release 0.41.0-debian-12-r1 (#91405)
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
GitHub
parent
fc6cf113c7
commit
6cf125ec0d
|
|
@ -17,7 +17,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
|
|||
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
|
||||
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
|
||||
COMPONENTS=( \
|
||||
"thanos-0.41.0-0-linux-${OS_ARCH}-debian-12" \
|
||||
"thanos-0.41.0-1-linux-${OS_ARCH}-debian-12" \
|
||||
) ; \
|
||||
for COMPONENT in "${COMPONENTS[@]}"; do \
|
||||
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
|
||||
|
|
@ -40,7 +40,7 @@ ARG TARGETARCH
|
|||
ENV OS_ARCH="${TARGETARCH:-amd64}"
|
||||
|
||||
LABEL org.opencontainers.image.base.name="scratch" \
|
||||
org.opencontainers.image.created="2026-02-12T11:52:59Z" \
|
||||
org.opencontainers.image.created="2026-03-06T18:32:29Z" \
|
||||
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
|
||||
org.opencontainers.image.title="thanos" \
|
||||
org.opencontainers.image.vendor="Broadcom, Inc." \
|
||||
|
|
@ -53,7 +53,7 @@ COPY --from=builder /opt/bitnami/thanos/licenses /opt/bitnami/thanos/licenses
|
|||
|
||||
ENV APP_VERSION="0.41.0" \
|
||||
BITNAMI_APP_NAME="thanos" \
|
||||
IMAGE_REVISION="0" \
|
||||
IMAGE_REVISION="1" \
|
||||
PATH="/opt/bitnami/thanos/bin:$PATH"
|
||||
|
||||
USER 1001
|
||||
|
|
|
|||
|
|
@ -1,7 +1,5 @@
|
|||
# Bitnami Secure Image for Thanos
|
||||
|
||||
## What is Thanos?
|
||||
|
||||
> 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](https://thanos.io/)
|
||||
|
|
@ -42,87 +40,16 @@ Non-root container images add an extra layer of security and are generally recom
|
|||
|
||||
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
|
||||
|
||||
## 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](https://github.com/bitnami/charts/tree/main/bitnami/thanos).
|
||||
|
||||
## Connecting to other containers
|
||||
|
||||
Using [Docker container networking](https://docs.docker.com/engine/userguide/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 thanos-network --driver bridge
|
||||
```
|
||||
|
||||
#### Step 2: Create a volume for Prometheus data
|
||||
|
||||
```console
|
||||
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:
|
||||
|
||||
```yaml
|
||||
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`.
|
||||
|
||||
```console
|
||||
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.
|
||||
|
||||
```console
|
||||
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`.
|
||||
|
||||
```console
|
||||
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/`
|
||||
|
||||
### Using Docker Compose
|
||||
|
||||
You can use the **docker-compose-cluster.yml** available on this repository to deploy an architecture like the one below:
|
||||
|
|
@ -177,12 +104,6 @@ docker logs thanos
|
|||
|
||||
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
|
||||
|
||||
## 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](https://github.com/bitnami/charts/tree/main/bitnami/thanos).
|
||||
|
||||
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](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md).
|
||||
|
||||
## License
|
||||
|
||||
Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.
|
||||
|
|
|
|||
Loading…
Reference in New Issue