From d93e26efbfc2711f28584b18b5124742e1eb3269 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Sat, 9 May 2026 01:53:40 +0200 Subject: [PATCH] [bitnami/schema-registry] Release 8.2.0-debian-12-r2 (#93016) Signed-off-by: Bitnami Bot --- .../schema-registry/8.2/debian-12/Dockerfile | 6 +-- bitnami/schema-registry/README.md | 39 ++++--------------- 2 files changed, 11 insertions(+), 34 deletions(-) diff --git a/bitnami/schema-registry/8.2/debian-12/Dockerfile b/bitnami/schema-registry/8.2/debian-12/Dockerfile index 3421ad92a7c3..e1832cdcf951 100644 --- a/bitnami/schema-registry/8.2/debian-12/Dockerfile +++ b/bitnami/schema-registry/8.2/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:12Z" \ + org.opencontainers.image.created="2026-05-08T22:49:38Z" \ 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" \ @@ -29,7 +29,7 @@ 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-17.0.18-10-1-linux-${OS_ARCH}-debian-12" \ + "jre-17.0.19-11-1-linux-${OS_ARCH}-debian-12" \ "schema-registry-8.2.0-0-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ @@ -52,7 +52,7 @@ RUN /opt/bitnami/scripts/java/postunpack.sh RUN /opt/bitnami/scripts/schema-registry/postunpack.sh ENV APP_VERSION="8.2.0" \ BITNAMI_APP_NAME="schema-registry" \ - IMAGE_REVISION="1" \ + IMAGE_REVISION="2" \ 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/README.md b/bitnami/schema-registry/README.md index fa73e2494430..e92ad5d17bf5 100644 --- a/bitnami/schema-registry/README.md +++ b/bitnami/schema-registry/README.md @@ -7,12 +7,18 @@ 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 schema-registry bitnami/schema-registry:latest ``` +## 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/schema-registry/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/schema-registry/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/schema-registry). + ## Why use Bitnami Secure Images? Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images? @@ -42,10 +48,6 @@ Subscribe to project updates by watching the [bitnami/containers GitHub reposito The Bitnami Confluent Schema Registry 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/schema-registry). - ## Configuration The following sections describe environment variables, Kafka and Zookeeper settings, security, and FIPS. @@ -93,8 +95,6 @@ The following tables list the main variables you can set. | `SCHEMA_REGISTRY_DEFAULT_LISTENERS` | Comma-separated list of listeners that listen for API requests over either HTTP or HTTPS. | `http://0.0.0.0:8081` | | `SCHEMA_REGISTRY_DEFAULT_KAFKA_BROKERS` | List of Kafka brokers to connect to. | `PLAINTEXT://localhost:9092` | -When you start the Confluent Schema Registry 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. Please note that some variables are only considered when the container is started for the first time. - #### Kafka settings Please check the configuration settings for the `kafka` service in the [Kafka's README file](https://github.com/bitnami/containers/tree/main/bitnami/kafka#configuration). @@ -109,29 +109,6 @@ The Schema Registry container can be set up to serve clients securely using TLS. 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`: - -```yaml -schema-registry: - image: bitnami/schema-registry:latest - ports: - - 8081:8081 - - 8082:8082 - depends_on: - - kafka - environment: - - SCHEMA_REGISTRY_KAFKA_BROKERS=PLAINTEXT://kafka:9092 - - SCHEMA_REGISTRY_HOST_NAME=schema-registry - - SCHEMA_REGISTRY_LISTENERS=http://0.0.0.0:8081,https://0.0.0.0:8082 - - SCHEMA_REGISTRY_SSL_KEYSTORE_PASSWORD=keystore - - SCHEMA_REGISTRY_SSL_TRUSTSTORE_PASSWORD=keystore - - SCHEMA_REGISTRY_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM=none - - SCHEMA_REGISTRY_CLIENT_AUTHENTICATION=REQUESTED - volumes: - - ./keystore.jks:/opt/bitnami/schema-registry/certs/keystore.jks:ro - - ./truststore.jks:/opt/bitnami/schema-registry/certs/truststore.jks:ro -``` - ### FIPS configuration in Bitnami Secure Images The Bitnami Confluent Schema Registry Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables: