public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[bitnami/elasticsearch] Release 9.3.4-debian-12-r0 (#92714) 

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-04-30 20:52:04 +02:00 committed by GitHub
parent 4cf1395247
commit 4df7f50d67
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 14 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
bitnami/elasticsearch/9.3/debian-12/Dockerfile
View File

@ -9,13 +9,13 @@ ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-08T18:11:11Z" \
org.opencontainers.image.created="2026-04-30T18:08:20Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/elasticsearch/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/elasticsearch" \
org.opencontainers.image.title="elasticsearch" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="9.3.3"
org.opencontainers.image.version="9.3.4"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@ -31,9 +31,9 @@ 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=( \
"yq-4.52.5-1-linux-${OS_ARCH}-debian-12" \
"java-21.0.10-10-0-linux-${OS_ARCH}-debian-12" \
"elasticsearch-9.3.3-0-linux-${OS_ARCH}-debian-12" \
"yq-4.53.2-0-linux-${OS_ARCH}-debian-12" \
"java-21.0.11-11-0-linux-${OS_ARCH}-debian-12" \
"elasticsearch-9.3.4-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@ -52,7 +52,7 @@ RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
COPY rootfs /
RUN /opt/bitnami/scripts/elasticsearch/postunpack.sh
RUN /opt/bitnami/scripts/java/postunpack.sh
ENV APP_VERSION="9.3.3" \
ENV APP_VERSION="9.3.4" \
BITNAMI_APP_NAME="elasticsearch" \
IMAGE_REVISION="0" \
JAVA_HOME="/opt/bitnami/java" \

31
bitnami/elasticsearch/README.md
View File

@ -11,7 +11,13 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name elasticsearch bitnami/elasticsearch:latest
```
You can find the available configuration options in the [Environment Variables](#environment-variables) section.
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/elasticsearch/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/elasticsearch/docker-compose.yml)
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/elasticsearch).
## Why use Bitnami Secure Images?
@ -46,10 +52,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
The Bitnami Elasticsearch Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
## 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/elasticsearch).
## Persisting your application
If you remove the container all your data will be lost, and the next time you run the image the application will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
@ -176,8 +178,6 @@ The following tables list the main variables you can set.
| `ES_JAVA_OPTS` | Elasticsearch supported Java options. | `${ES_JAVA_OPTS:-} ${JAVA_TOOL_OPTIONS:-}` |
| `CLI_JAVA_OPTS` | Elasticsearch CLI supported Java options. | `${CLI_JAVA_OPTS:-} ${JAVA_TOOL_OPTIONS:-}` |
When you start the elasticsearch image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line.
### Configuration file
In order to use a custom configuration file instead of the default one provided out of the box, you can create a file named `elasticsearch.yml` and mount it at `/opt/bitnami/elasticsearch/config/elasticsearch.yml` to overwrite the default configuration.
@ -223,22 +223,7 @@ The Bitnami Elasticsearch Docker image from the [Bitnami Secure Images](https://
## Logging
The Bitnami Elasticsearch Docker image sends the container logs to the `stdout`. To view the logs:
```console
docker logs elasticsearch
```
or using Docker Compose:
```console
docker-compose logs elasticsearch
```
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.
Additionally, in case you'd like to modify Elasticsearch logging configuration, it can be done by overwriting the file `/opt/bitnami/elasticsearch/config/log4j2.properties`.
The syntax of this file can be found in Elasticsearch [logging documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/logging.html).
The Bitnami Elasticsearch Docker image sends the container logs to the `stdout`. 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.
## Notable Changes