From 91093b77610a45a86bde58367f90abacf451c33d Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Thu, 19 Feb 2026 06:45:36 +0100 Subject: [PATCH] [bitnami/schema-registry] Release 8.1.1-debian-12-r3 (#90996) Signed-off-by: Bitnami Bot --- bitnami/schema-registry/8.1/debian-12/Dockerfile | 4 ++-- .../prebuildfs/opt/bitnami/scripts/libbitnami.sh | 2 -- bitnami/schema-registry/README.md | 14 +------------- 3 files changed, 3 insertions(+), 17 deletions(-) diff --git a/bitnami/schema-registry/8.1/debian-12/Dockerfile b/bitnami/schema-registry/8.1/debian-12/Dockerfile index b30e8579d99d..60d49239fee4 100644 --- a/bitnami/schema-registry/8.1/debian-12/Dockerfile +++ b/bitnami/schema-registry/8.1/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-01-28T18:59:04Z" \ + org.opencontainers.image.created="2026-02-19T04:45:34Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/schema-registry/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/schema-registry" \ @@ -52,7 +52,7 @@ RUN /opt/bitnami/scripts/java/postunpack.sh RUN /opt/bitnami/scripts/schema-registry/postunpack.sh ENV APP_VERSION="8.1.1" \ BITNAMI_APP_NAME="schema-registry" \ - IMAGE_REVISION="2" \ + IMAGE_REVISION="3" \ JAVA_HOME="/opt/bitnami/java" \ PATH="/opt/bitnami/java/bin:/opt/bitnami/schema-registry/bin:/opt/bitnami/common/bin:$PATH" diff --git a/bitnami/schema-registry/8.1/debian-12/prebuildfs/opt/bitnami/scripts/libbitnami.sh b/bitnami/schema-registry/8.1/debian-12/prebuildfs/opt/bitnami/scripts/libbitnami.sh index 93cf59b06232..b134a91c7e24 100644 --- a/bitnami/schema-registry/8.1/debian-12/prebuildfs/opt/bitnami/scripts/libbitnami.sh +++ b/bitnami/schema-registry/8.1/debian-12/prebuildfs/opt/bitnami/scripts/libbitnami.sh @@ -46,8 +46,6 @@ print_image_welcome_page() { info "" info "${BOLD}Welcome to the Bitnami ${BITNAMI_APP_NAME} container${RESET}" - info "Subscribe to project updates by watching ${BOLD}${github_url}${RESET}" - info "${YELLOW}NOTICE: Starting August 28th, 2025, only a limited subset of images/charts will remain available for free. Backup will be available for some time at the 'Bitnami Legacy' repository. More info at https://github.com/bitnami/containers/issues/83267${RESET}" info "" } diff --git a/bitnami/schema-registry/README.md b/bitnami/schema-registry/README.md index 9d625046bc0c..867b022dca7a 100644 --- a/bitnami/schema-registry/README.md +++ b/bitnami/schema-registry/README.md @@ -34,10 +34,6 @@ If you are looking for our previous generation of images based on Debian Linux, Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html). -You can see the equivalence between the different tags by taking a look at the `tags-info.yaml` file present in the branch folder, i.e `bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml`. - -Subscribe to project updates by watching the [bitnami/containers GitHub repo](https://github.com/bitnami/containers). - ## Get this image The recommended way to get the Bitnami schema-registry Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/schema-registry). @@ -137,7 +133,7 @@ Please check the configuration settings for the Kakfa service in the [Zookeeper' The Schema Registry container can be setup to serve clients securely via TLS. To do so, specify the listener protocol as **https** in the `SCHEMA_REGISTRY_LISTENERS` environment variable (e.g. SCHEMA_REGISTRY_LISTENERS=`http://0.0.0.0:8081`,`https://0.0.0.0:8082`). -The keystore and trustore **must** be mounted in the `/opt/bitnami/schema-registry/certs` directory as `ssl.keystore.jks` and `ssl.truststore.jks` respectively. Currently, only JKS formats are supported. Note that the environment variables `SCHEMA_REGISTRY_SSL_KEYSTORE_LOCATION` or `SCHEMA_REGISTRY_SSL_TRUSTSTORE_LOCATION` **will not** override the expected location or file names. Please follow the instructions provided or you will get this error at startup: *ERROR ==> In order to configure HTTPS access, you must mount your ssl.keystore.jks (and optionally the ssl.truststore.jks) to the /opt/bitnami/schema-registry/certs directory*. +The keystore and truststore **must** be mounted in the `/opt/bitnami/schema-registry/certs` directory as `ssl.keystore.jks` and `ssl.truststore.jks` respectively. Currently, only JKS formats are supported. Note that the environment variables `SCHEMA_REGISTRY_SSL_KEYSTORE_LOCATION` or `SCHEMA_REGISTRY_SSL_TRUSTSTORE_LOCATION` **will not** override the expected location or file names. Please follow the instructions provided or you will get this error at startup: *ERROR ==> In order to configure HTTPS access, you must mount your ssl.keystore.jks (and optionally the ssl.truststore.jks) to the /opt/bitnami/schema-registry/certs directory*. Here is a `docker-compose.yml` example that exposes a TLS listener on port `8082`: @@ -174,14 +170,6 @@ Please be aware this file has not undergone internal testing. Consequently, we a If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md). -## Contributing - -We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/containers/issues) or submitting a [pull request](https://github.com/bitnami/containers/pulls) with your contribution. - -## Issues - -If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/containers/issues/new/choose). For us to provide better support, be sure to fill the issue template. - ## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.