[bitnami/zookeeper] Release 3.7.1-debian-11-r94 (#24442)
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
parent
25fd9cadc0
commit
cf158b893d
|
|
@ -2,11 +2,11 @@ FROM docker.io/bitnami/minideb:bullseye
|
|||
|
||||
ARG TARGETARCH
|
||||
|
||||
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
|
||||
org.opencontainers.image.description="Application packaged by Bitnami" \
|
||||
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
|
||||
org.opencontainers.image.created="2023-02-17T18:45:03Z" \
|
||||
org.opencontainers.image.description="Application packaged by VMware, Inc" \
|
||||
org.opencontainers.image.licenses="Apache-2.0" \
|
||||
org.opencontainers.image.ref.name="3.7.1-debian-11-r93" \
|
||||
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/zookeeper" \
|
||||
org.opencontainers.image.ref.name="3.7.1-debian-11-r94" \
|
||||
org.opencontainers.image.title="zookeeper" \
|
||||
org.opencontainers.image.vendor="VMware, Inc." \
|
||||
org.opencontainers.image.version="3.7.1"
|
||||
|
|
@ -23,10 +23,10 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
|
|||
RUN install_packages ca-certificates curl netcat procps xmlstarlet zlib1g
|
||||
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
|
||||
COMPONENTS=( \
|
||||
"wait-for-port-1.0.6-0-linux-${OS_ARCH}-debian-11" \
|
||||
"java-11.0.18-10-0-linux-${OS_ARCH}-debian-11" \
|
||||
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
|
||||
"zookeeper-3.7.1-158-linux-${OS_ARCH}-debian-11" \
|
||||
"wait-for-port-1.0.6-1-linux-${OS_ARCH}-debian-11" \
|
||||
"java-11.0.18-10-1-linux-${OS_ARCH}-debian-11" \
|
||||
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
|
||||
"zookeeper-3.7.1-159-linux-${OS_ARCH}-debian-11" \
|
||||
) && \
|
||||
for COMPONENT in "${COMPONENTS[@]}"; do \
|
||||
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
|
||||
|
|
|
|||
|
|
@ -1,30 +1,30 @@
|
|||
{
|
||||
"gosu": {
|
||||
"arch": "amd64",
|
||||
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
|
||||
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
|
||||
"distro": "debian-11",
|
||||
"type": "NAMI",
|
||||
"version": "1.16.0-1"
|
||||
"version": "1.16.0-2"
|
||||
},
|
||||
"java": {
|
||||
"arch": "amd64",
|
||||
"digest": "f8c3013925073f94edc495584b76f0b08c867ba35c524e2b262e47e815a443b9",
|
||||
"digest": "cd40a6df619d734d300324ad671f34323152e84682bc998da1330f1a7f0acfa6",
|
||||
"distro": "debian-11",
|
||||
"type": "NAMI",
|
||||
"version": "11.0.18-10-0"
|
||||
"version": "11.0.18-10-1"
|
||||
},
|
||||
"wait-for-port": {
|
||||
"arch": "amd64",
|
||||
"digest": "f9199cd66b92fef328ecfbc5ffbc8f14be33257a4e34b8c6ba35a730c5a2f59d",
|
||||
"digest": "be7c393d598ddf16d1c3c008a67b87879e48aca62071a208583390f2b41e6744",
|
||||
"distro": "debian-11",
|
||||
"type": "NAMI",
|
||||
"version": "1.0.6-0"
|
||||
"version": "1.0.6-1"
|
||||
},
|
||||
"zookeeper": {
|
||||
"arch": "amd64",
|
||||
"digest": "b92653f4db2f35421e2113a39660cd63a8d6c02709c22d7805393c04b2627f21",
|
||||
"digest": "49481d40484773893df8d1d4877c260385adab1d22a3b1f376f933515cffbf39",
|
||||
"distro": "debian-11",
|
||||
"type": "NAMI",
|
||||
"version": "3.7.1-158"
|
||||
"version": "3.7.1-159"
|
||||
}
|
||||
}
|
||||
|
|
@ -138,7 +138,7 @@ docker run -it --rm \
|
|||
bitnami/zookeeper:latest zkCli.sh -server zookeeper-server:2181 get /
|
||||
```
|
||||
|
||||
### Using Docker Compose
|
||||
### Using a Docker Compose file
|
||||
|
||||
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the Apache ZooKeeper server from your own custom application image which is identified in the following snippet by the service name `myapp`.
|
||||
|
||||
|
|
@ -236,7 +236,7 @@ services:
|
|||
...
|
||||
```
|
||||
|
||||
### ZooKeeper configuration
|
||||
### Apache ZooKeeper Configuration
|
||||
|
||||
The image looks for configuration in the `conf/` directory of `/opt/bitnami/zookeeper`.
|
||||
|
||||
|
|
@ -325,7 +325,7 @@ services:
|
|||
|
||||
### Setting up an Apache ZooKeeper ensemble
|
||||
|
||||
A Apache ZooKeeper (<https://zookeeper.apache.org/doc/r3.1.2/zookeeperAdmin.html>) cluster can easily be setup with the Bitnami Apache ZooKeeper Docker image using the following environment variables:
|
||||
A Apache ZooKeeper (https://zookeeper.apache.org/doc/r3.1.2/zookeeperAdmin.html) cluster can easily be setup with the Bitnami Apache ZooKeeper Docker image using the following environment variables:
|
||||
|
||||
* `ZOO_SERVERS`: Comma, space or semi-colon separated list of servers. This can be done with or without specifying the ID of the server in the ensemble. No defaults. Examples:
|
||||
* without Server ID - zoo1:2888:3888,zoo2:2888:3888
|
||||
|
|
@ -433,7 +433,7 @@ services:
|
|||
- ZOO_SERVERS=zookeeper1:2888:3888,zookeeper2:2888:3888,0.0.0.0:2888:3888
|
||||
```
|
||||
|
||||
### Start Zookeeper with TLS
|
||||
### Start Apache ZooKeeper with TLS
|
||||
|
||||
```console
|
||||
docker run --name zookeeper \
|
||||
|
|
|
|||
Loading…
Reference in New Issue