From 2c9ab523ccc49e98bf4e625945f63214bfd3fc00 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Sat, 20 Jan 2024 06:08:43 +0100 Subject: [PATCH] [bitnami/schema-registry] Release 7.5.3-debian-11-r1 (#55176) Signed-off-by: Bitnami Containers --- .../schema-registry/7.5/debian-11/Dockerfile | 7 +-- .../opt/bitnami/.bitnami_components.json | 2 +- bitnami/schema-registry/README.md | 48 +++++++++++-------- 3 files changed, 33 insertions(+), 24 deletions(-) diff --git a/bitnami/schema-registry/7.5/debian-11/Dockerfile b/bitnami/schema-registry/7.5/debian-11/Dockerfile index 26e2d22acca1..f3552b81120e 100644 --- a/bitnami/schema-registry/7.5/debian-11/Dockerfile +++ b/bitnami/schema-registry/7.5/debian-11/Dockerfile @@ -8,10 +8,10 @@ ARG TARGETARCH LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \ org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \ - org.opencontainers.image.created="2024-01-06T02:35:22Z" \ + org.opencontainers.image.created="2024-01-20T03:51:37Z" \ org.opencontainers.image.description="Application packaged by VMware, Inc" \ org.opencontainers.image.licenses="Apache-2.0" \ - org.opencontainers.image.ref.name="7.5.3-debian-11-r0" \ + org.opencontainers.image.ref.name="7.5.3-debian-11-r1" \ org.opencontainers.image.title="schema-registry" \ org.opencontainers.image.vendor="VMware, Inc." \ org.opencontainers.image.version="7.5.3" @@ -27,7 +27,7 @@ SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"] RUN install_packages ca-certificates curl netcat-openbsd procps zlib1g RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \ COMPONENTS=( \ - "java-17.0.9-11-6-linux-${OS_ARCH}-debian-11" \ + "java-17.0.10-13-0-linux-${OS_ARCH}-debian-11" \ "schema-registry-7.5.3-0-linux-${OS_ARCH}-debian-11" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ @@ -43,6 +43,7 @@ RUN apt-get autoremove --purge -y curl && \ apt-get update && apt-get upgrade -y && \ apt-get clean && rm -rf /var/lib/apt/lists /var/cache/apt/archives RUN chmod g+rwX /opt/bitnami +RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true COPY rootfs / RUN /opt/bitnami/scripts/java/postunpack.sh diff --git a/bitnami/schema-registry/7.5/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json b/bitnami/schema-registry/7.5/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json index c6293366ca6f..eb33ae616923 100644 --- a/bitnami/schema-registry/7.5/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json +++ b/bitnami/schema-registry/7.5/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json @@ -3,7 +3,7 @@ "arch": "amd64", "distro": "debian-11", "type": "NAMI", - "version": "17.0.9-11-6" + "version": "17.0.10-13-0" }, "schema-registry": { "arch": "amd64", diff --git a/bitnami/schema-registry/README.md b/bitnami/schema-registry/README.md index 686d25abff21..8635c69bea68 100644 --- a/bitnami/schema-registry/README.md +++ b/bitnami/schema-registry/README.md @@ -58,6 +58,28 @@ docker build -t bitnami/APP:latest . ### Environment variables +#### Customizable environment variables + +| Name | Description | Default Value | +|------------------------------------|-----------------------------------------------------------------------------------------------|-------------------------------------| +| `SCHEMA_REGISTRY_MOUNTED_CONF_DIR` | Directory for including custom configuration files (that override the default generated ones) | `${SCHEMA_REGISTRY_VOLUME_DIR}/etc` | + +#### Read-only environment variables + +| Name | Description | Value | +|-----------------------------------------|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| `SCHEMA_REGISTRY_BASE_DIR` | Base path for SCHEMA REGISTRY files. | `${BITNAMI_ROOT_DIR}/schema-registry` | +| `SCHEMA_REGISTRY_VOLUME_DIR` | SCHEMA REGISTRY directory for persisted files. | `${BITNAMI_VOLUME_DIR}/schema-registry` | +| `SCHEMA_REGISTRY_BIN_DIR` | SCHEMA REGISTRY certificates directory. | `${SCHEMA_REGISTRY_BASE_DIR}/bin` | +| `SCHEMA_REGISTRY_CERTS_DIR` | SCHEMA REGISTRY certificates directory. | `${SCHEMA_REGISTRY_BASE_DIR}/certs` | +| `SCHEMA_REGISTRY_CONF_DIR` | SCHEMA REGISTRY configuration directory. | `${SCHEMA_REGISTRY_BASE_DIR}/etc` | +| `SCHEMA_REGISTRY_LOGS_DIR` | SCHEMA REGISTRY logs directory. | `${SCHEMA_REGISTRY_BASE_DIR}/logs` | +| `SCHEMA_REGISTRY_CONF_FILE` | Main SCHEMA REGISTRY configuration file. | `${SCHEMA_REGISTRY_CONF_DIR}/schema-registry/schema-registry.properties` | +| `SCHEMA_REGISTRY_DAEMON_USER` | Users that will execute the SCHEMA REGISTRY Server process. | `schema-registry` | +| `SCHEMA_REGISTRY_DAEMON_GROUP` | Group that will execute the SCHEMA REGISTRY Server process. | `schema-registry` | +| `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. If you want to add a new environment variable: * For docker-compose add the variable name and value under the application section in the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/schema-registry/docker-compose.yml) file present in this repository: @@ -80,26 +102,6 @@ When you start the Confluent Schema Registry image, you can adjust the configura bitnami/schema-registry:latest ``` -Available environment variables: - -#### Schema Registry settings - -* `SCHEMA_REGISTRY_KAFKA_BROKERS`: List of Kafka brokers to connect to. Default: **PLAINTEXT://localhost:9092**. -* `SCHEMA_REGISTRY_ADVERTISED_HOSTNAME`: Advertised hostname in ZooKeeper. Default: **container IP**. -* `SCHEMA_REGISTRY_KAFKA_KEYSTORE_PASSWORD`: Password to access the keystore. Default: **empty value**. -* `SCHEMA_REGISTRY_KAFKA_KEY_PASSWORD`: Password to be able to used ssl secured kafka broker with Schema Registry. Default: **empty value**. -* `SCHEMA_REGISTRY_KAFKA_TRUSTSTORE_PASSWORD`: Password to access the truststore. Default: **empty value**. -* `SCHEMA_REGISTRY_KAFKA_SASL_USER`: SASL user to authenticate with Kafka. Default: **empty value**. -* `SCHEMA_REGISTRY_KAFKA_SASL_PASSWORD`: SASL password to authenticate with Kafka. Default: **empty value**. -* `SCHEMA_REGISTRY_LISTENERS`: Comma-separated list of listeners that listen for API requests over either HTTP or HTTPS. Default: ****. -* `SCHEMA_REGISTRY_SSL_KEYSTORE_PASSWORD`: Password to access the SSL keystore. Default: **empty value**. -* `SCHEMA_REGISTRY_SSL_KEY_PASSWORD`: Password to access the SSL key. Default: **empty value**. -* `SCHEMA_REGISTRY_SSL_TRUSTSTORE_PASSWORD`: Password to access the SSL truststore. Default: **empty value**. -* `SCHEMA_REGISTRY_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM`: Endpoint identification algorithm to validate the server hostname using the server certificate. Default: **empty value**. -* `SCHEMA_REGISTRY_CLIENT_AUTHENTICATION`: Client authentication configuration. Valid options: `NONE`, `REQUESTED`, or `REQUIRED`. -* `SCHEMA_REGISTRY_AVRO_COMPATIBILY_LEVEL`: The Avro compatibility type. Valid options: `NONE`, `BACKWARD`, `BACKWARD_TRANSITIVE`, `FORWARD`, `FORWARD_TRANSITIVE`, `FULL`, or `FULL_TRANSITIVE`. -* `SCHEMA_REGISTRY_DEBUG`: Enable Schema Registry debug logs. Valid options: true or false. Default: **false**. - #### Kafka settings Please check the configuration settings for the Kakfa service in the [Kafka's README file](https://github.com/bitnami/containers/tree/main/bitnami/kafka#configuration). @@ -108,6 +110,12 @@ Please check the configuration settings for the Kakfa service in the [Kafka's RE Please check the configuration settings for the Kakfa service in the [Zookeeper's README file](https://github.com/bitnami/containers/tree/main/bitnami/zookeeper#configuration). +## 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). + +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.