public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-18 00:16:39 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/opensearch] Release 3.6.0-debian-12-r0 (#92540)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-04-17 12:04:53 +02:00
committed by GitHub
parent 8991bddadd
commit 38b2bc6faa
2 changed files with 14 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/opensearch/3/debian-12/Dockerfile
+6 -6
View File
@@ -9,13 +9,13 @@ ARG OPENSEARCH_PLUGINS
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-08T22:18:46Z" \
org.opencontainers.image.created="2026-04-17T09:12:49Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/opensearch/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/opensearch" \
org.opencontainers.image.title="opensearch" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="3.5.0"
org.opencontainers.image.version="3.6.0"
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" \
"yq-4.53.2-0-linux-${OS_ARCH}-debian-12" \
"jre-21.0.10-10-0-linux-${OS_ARCH}-debian-12" \
"opensearch-3.5.0-0-linux-${OS_ARCH}-debian-12" \
"opensearch-3.6.0-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -52,9 +52,9 @@ RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
COPY rootfs /
RUN /opt/bitnami/scripts/opensearch/postunpack.sh
RUN /opt/bitnami/scripts/java/postunpack.sh
ENV APP_VERSION="3.5.0" \
ENV APP_VERSION="3.6.0" \
BITNAMI_APP_NAME="opensearch" \
IMAGE_REVISION="3" \
IMAGE_REVISION="0" \
JAVA_HOME="/opt/bitnami/java" \
LD_LIBRARY_PATH="/opt/bitnami/opensearch/jdk/lib:/opt/bitnami/opensearch/jdk/lib/server:/opt/bitnami/opensearch/plugins/opensearch-knn/lib:$LD_LIBRARY_PATH" \
OPENSEARCH_JAVA_HOME="/opt/bitnami/java"
bitnami/opensearch/README.md
+8 -36
View File
@@ -7,13 +7,17 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
## TL;DR
Use this quick command to run the container.
```console
docker run --name opensearch bitnami/opensearch: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/opensearch/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/opensearch/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/opensearch).
## Why use Bitnami Secure Images?
@@ -48,10 +52,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
The Bitnami OpenSearch 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/opensearch).
## 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.
@@ -170,8 +170,6 @@ The following tables list the main variables you can set.
| `OPENSEARCH_DAEMON_GROUP` | Opensearch system group | `opensearch` |
| `OPENSEARCH_USERNAME` | Username of the Opensearch superuser. | `admin` |
When you start the opensearch 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.
### Setting up a cluster
A cluster can easily be setup with the Bitnami OpenSearch Docker Image using the following environment variables:
@@ -202,17 +200,6 @@ docker run -d --name opensearch \
bitnami/opensearch:latest
```
or by changing the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/opensearch/docker-compose.yml) file present in this repository:
```yaml
opensearch:
...
volumes:
- /path/to/opensearch.yml:/opt/bitnami/opensearch/config/opensearch.yml
- /path/to/opensearch-data-persistence:/bitnami/opensearch/data
...
```
Please, note that the whole configuration file will be replaced by the provided, default one; ensure that the syntax and fields you provide are properly set and exhaustive.
If you would rather extend than replace the default configuration with your settings, mount your custom configuration file at `/opt/bitnami/opensearch/config/my_opensearch.yml`.
@@ -258,22 +245,7 @@ The Bitnami OpenSearch Docker image from the [Bitnami Secure Images](https://go-
## Logging
The Bitnami OpenSearch Docker image sends the container logs to the `stdout`. To view the logs:
```console
docker logs opensearch
```
or using Docker Compose:
```console
docker-compose logs opensearch
```
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 OpenSearch logging configuration, it can be done by overwriting the file `/opt/bitnami/opensearch/config/log4j2.properties`.
The syntax of this file can be found in OpenSearch [logging documentation](https://www.elastic.co/guide/en/opensearch/reference/current/logging.html).
The Bitnami OpenSearch 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.
## License