diff --git a/bitnami/solr/10/debian-12/Dockerfile b/bitnami/solr/10/debian-12/Dockerfile index 3594ebc6ce35..5ec8cf54372b 100644 --- a/bitnami/solr/10/debian-12/Dockerfile +++ b/bitnami/solr/10/debian-12/Dockerfile @@ -8,7 +8,7 @@ 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-08T21:34:20Z" \ + org.opencontainers.image.created="2026-04-22T17:29:06Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/solr/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/solr" \ @@ -29,8 +29,8 @@ 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=( \ - "jre-21.0.10-10-0-linux-${OS_ARCH}-debian-12" \ - "solr-10.0.0-1-linux-${OS_ARCH}-debian-12" \ + "jre-21.0.11-11-0-linux-${OS_ARCH}-debian-12" \ + "solr-10.0.0-2-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -51,7 +51,7 @@ RUN /opt/bitnami/scripts/java/postunpack.sh RUN /opt/bitnami/scripts/solr/postunpack.sh ENV APP_VERSION="10.0.0" \ BITNAMI_APP_NAME="solr" \ - IMAGE_REVISION="4" \ + IMAGE_REVISION="5" \ JAVA_HOME="/opt/bitnami/java" \ PATH="/opt/bitnami/java/bin:/opt/bitnami/solr/bin:/opt/bitnami/solr/prometheus-exporter/bin:/opt/bitnami/solr/contrib/prometheus-exporter/bin:$PATH" diff --git a/bitnami/solr/10/debian-12/rootfs/opt/bitnami/scripts/libsolr.sh b/bitnami/solr/10/debian-12/rootfs/opt/bitnami/scripts/libsolr.sh index cbc1c1c724d1..003b5a5f7b8f 100644 --- a/bitnami/solr/10/debian-12/rootfs/opt/bitnami/scripts/libsolr.sh +++ b/bitnami/solr/10/debian-12/rootfs/opt/bitnami/scripts/libsolr.sh @@ -649,6 +649,10 @@ solr_initialize() { solr_wait_for_zk_root fi fi + + # Persistence changes break adding Solr cores. Persist data in cloud mode only + info "Persisting Solr installation" + persist_app "$app_name" "$SOLR_DATA_TO_PERSIST" else info "Deploying Solr from scratch" @@ -664,9 +668,6 @@ solr_initialize() { solr_stop fi - - info "Persisting Solr installation" - persist_app "$app_name" "$SOLR_DATA_TO_PERSIST" else info "Restoring persisted Solr installation" diff --git a/bitnami/solr/README.md b/bitnami/solr/README.md index d687104eb098..2621e52bfdb8 100644 --- a/bitnami/solr/README.md +++ b/bitnami/solr/README.md @@ -11,7 +11,13 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema docker run --name solr bitnami/solr: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/solr/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/solr/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/solr). ## Why use Bitnami Secure Images? @@ -42,10 +48,6 @@ Subscribe to project updates by watching the [bitnami/containers GitHub reposito The Bitnami Apache Solr 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/solr). - ## Persisting your application If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed. @@ -119,8 +121,6 @@ The following tables list the main variables you can set. | `SOLR_DAEMON_GROUP` | Solr system group | `solr` | | `SOLR_ZK_CONNECTION_TIMEOUT` | ZooKeeper connection attempt timeout. | `10` | -When you start the solr 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. - ### Using your Apache Solr Cores configuration files In order to load your own configuration files, you will have to make them available to the container. You can do it mounting a [volume](https://docs.docker.com/engine/tutorials/dockervolumes/) in the desired location and setting the environment variable with the customized value (as it is pointed above, the default value is **data_driven_schema_configs**). @@ -134,19 +134,7 @@ The Bitnami Apache Solr Docker image from the [Bitnami Secure Images](https://go ## Logging -The Bitnami Solr Docker image sends the container logs to the `stdout`. To view the logs: - -```console -docker logs solr -``` - -or using Docker Compose: - -```console -docker-compose logs solr -``` - -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. +The Bitnami Apache Solr 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