[bitnami/influxdb] Release 2.6.1-debian-11-r18 (#24307)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-02-17 17:34:19 +01:00 committed by GitHub
parent 59e1536054
commit 8a9b41c668
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 14 additions and 14 deletions

View File

@ -2,11 +2,11 @@ FROM docker.io/bitnami/minideb:bullseye
ARG TARGETARCH
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
org.opencontainers.image.description="Application packaged by Bitnami" \
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-02-17T16:17:05Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="2.6.1-debian-11-r17" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/influxdb" \
org.opencontainers.image.ref.name="2.6.1-debian-11-r18" \
org.opencontainers.image.title="influxdb" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="2.6.1"
@ -22,9 +22,9 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl libgcc-s1 procps
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"wait-for-port-1.0.6-0-linux-${OS_ARCH}-debian-11" \
"influxdb-2.6.1-1-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"wait-for-port-1.0.6-1-linux-${OS_ARCH}-debian-11" \
"influxdb-2.6.1-2-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

View File

@ -1,23 +1,23 @@
{
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"influxdb": {
"arch": "amd64",
"digest": "ef7cfb73939803dd4f8f43ac3b35419aefb12e54db2d767fae430978375b7a8b",
"digest": "6074577e64c037d101e763eeedc1be100b9eb123171ea02ea33d24c6cf4c9dec",
"distro": "debian-11",
"type": "NAMI",
"version": "2.6.1-1"
"version": "2.6.1-2"
},
"wait-for-port": {
"arch": "amd64",
"digest": "f9199cd66b92fef328ecfbc5ffbc8f14be33257a4e34b8c6ba35a730c5a2f59d",
"digest": "be7c393d598ddf16d1c3c008a67b87879e48aca62071a208583390f2b41e6744",
"distro": "debian-11",
"type": "NAMI",
"version": "1.0.6-0"
"version": "1.0.6-1"
}
}

View File

@ -126,7 +126,7 @@ docker run -it --rm \
bitnami/influxdb:latest influx -host influxdb-server
```
### Using Docker Compose
### Using a Docker Compose file
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `my-network`. In this example we assume that you want to connect to the InfluxDB (TM) server from your own custom application image which is identified in the following snippet by the service name `myapp`.