[bitnami/elasticsearch] Release 8.6.2-debian-11-r0 (#24251)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-02-17 16:18:37 +01:00 committed by GitHub
parent b23b85fb3d
commit fd752b62b6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 24 additions and 24 deletions

View File

@ -4,14 +4,14 @@ ARG ELASTICSEARCH_PLUGINS
ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
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-17T14:45:23Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="8.6.1-debian-11-r6" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/elasticsearch" \
org.opencontainers.image.ref.name="8.6.2-debian-11-r0" \
org.opencontainers.image.title="elasticsearch" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="8.6.1"
org.opencontainers.image.version="8.6.2"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@ -25,10 +25,10 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl libasound2-dev libc6 libfreetype6 libfreetype6-dev libgcc1 procps zlib1g
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"yq-4.30.8-1-linux-${OS_ARCH}-debian-11" \
"java-17.0.6-10-0-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"elasticsearch-8.6.1-2-linux-${OS_ARCH}-debian-11" \
"yq-4.30.8-2-linux-${OS_ARCH}-debian-11" \
"java-17.0.6-10-1-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
"elasticsearch-8.6.2-0-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@ -46,7 +46,7 @@ RUN chmod g+rwX /opt/bitnami
COPY rootfs /
RUN /opt/bitnami/scripts/elasticsearch/postunpack.sh
RUN /opt/bitnami/scripts/java/postunpack.sh
ENV APP_VERSION="8.6.1" \
ENV APP_VERSION="8.6.2" \
BITNAMI_APP_NAME="elasticsearch" \
ES_JAVA_HOME="/opt/bitnami/java" \
JAVA_HOME="/opt/bitnami/java" \

View File

@ -1,30 +1,30 @@
{
"elasticsearch": {
"arch": "amd64",
"digest": "d00fbc50c43932f70f8067810a04ea7db67fe079eb1d0afbd95742862d7464b8",
"digest": "8928590bec3c6efe7f0e4f4694574d471a8bd3658208182916ed2539bb9090f1",
"distro": "debian-11",
"type": "NAMI",
"version": "8.6.1-2"
"version": "8.6.2-0"
},
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"java": {
"arch": "amd64",
"digest": "a89ace6cbda8b33cc4e18bb0954e8b3316eb810f4f832516d60dfb49bd5f20f2",
"digest": "616d810dc3a926249db7843e25676da79c536a6fb01af626cd6ce88d7aa4c3e1",
"distro": "debian-11",
"type": "NAMI",
"version": "17.0.6-10-0"
"version": "17.0.6-10-1"
},
"yq": {
"arch": "amd64",
"digest": "33fec06619aa3c1f7ea3c2516bf36f79af01354972ff06998ca6fe1d65078998",
"digest": "2fcd60b9977991e83f7066cf6da2c319b21483cdc67597625af37fa753534faf",
"distro": "debian-11",
"type": "NAMI",
"version": "4.30.8-1"
"version": "4.30.8-2"
}
}

View File

@ -1,5 +1,5 @@
rolling-tags:
- "8"
- 8-debian-11
- 8.6.1
- 8.6.2
- latest

View File

@ -146,7 +146,7 @@ docker run -d --name myapp \
> 1. Please update the **YOUR_APPLICATION_IMAGE_** placeholder in the above snippet with your application image
> 2. In your application container, use the hostname `elasticsearch-server` to connect to the Elasticsearch 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 `app-tier`. In this example we assume that you want to connect to the Elasticsearch server from your own custom application image which is identified in the following snippet by the service name `myapp`.
@ -198,7 +198,7 @@ elasticsearch:
* For manual execution add a `-e` option with each variable and value:
```console
docker run -d --name elasticsearch \
$ docker run -d --name elasticsearch \
-p 9201:9201 --network=elasticsearch_network \
-e ELASTICSEARCH_PORT_NUMBER=9201 \
-v /path/to/elasticsearch-data-persistence:/bitnami/elasticsearch/data \
@ -470,12 +470,12 @@ docker-compose up elasticsearch
* Backwards compatibility is not guaranteed when data is persisted using docker-compose. You can use the workaround below to overcome it:
```console
docker-compose down
$ docker-compose down
# Change the mount point
sed -i -e 's#elasticsearch_data:/bitnami#elasticsearch_data:/bitnami/elasticsearch/data#g' docker-compose.yml
# Pull the latest bitnami/elasticsearch image
docker pull bitnami/elasticsearch:latest
docker-compose up -d
$ docker pull bitnami/elasticsearch:latest
$ docker-compose up -d
```
### 6.2.3-r7 & 5.6.4-r18