public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-18 04:16:52 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/zookeeper] Release 3.8.0-debian-11-r40 (#8158)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2022-09-28 11:06:06 +00:00
committed by GitHub
parent eb8785e16c
commit 9ff1827b6e
2 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/zookeeper/3.8/debian-11/Dockerfile
+1 -1
View File
@@ -4,7 +4,7 @@ ARG TARGETARCH
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
org.opencontainers.image.description="Application packaged by Bitnami" \
org.opencontainers.image.ref.name="3.8.0-debian-11-r39" \
org.opencontainers.image.ref.name="3.8.0-debian-11-r40" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/zookeeper" \
org.opencontainers.image.title="zookeeper" \
org.opencontainers.image.vendor="VMware, Inc." \
bitnami/zookeeper/README.md
+18 -18
View File
@@ -50,7 +50,7 @@ Non-root container images add an extra layer of security and are generally recom
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
* [`3.8`, `3.8-debian-11`, `3.8.0`, `3.8.0-debian-11-r39`, `latest` (3.8/debian-11/Dockerfile)](https://github.com/bitnami/containers/blob/main/bitnami/zookeeper/3.8/debian-11/Dockerfile)
* [`3.8`, `3.8-debian-11`, `3.8.0`, `3.8.0-debian-11-r40`, `latest` (3.8/debian-11/Dockerfile)](https://github.com/bitnami/containers/blob/main/bitnami/zookeeper/3.8/debian-11/Dockerfile)
* [`3.7`, `3.7-debian-11`, `3.7.1`, `3.7.1-debian-11-r44` (3.7/debian-11/Dockerfile)](https://github.com/bitnami/containers/blob/main/bitnami/zookeeper/3.7/debian-11/Dockerfile)
* [`3.6`, `3.6-debian-11`, `3.6.3`, `3.6.3-debian-11-r44` (3.6/debian-11/Dockerfile)](https://github.com/bitnami/containers/blob/main/bitnami/zookeeper/3.6/debian-11/Dockerfile)
@@ -181,20 +181,20 @@ The configuration can easily be setup with the Bitnami Apache ZooKeeper Docker i
- `ZOO_PORT_NUMBER`: Apache ZooKeeper client port. Default: **2181**
- `ZOO_SERVER_ID`: ID of the server in the ensemble. Default: **1**
- `ZOO_TICK_TIME`: Basic time unit in milliseconds used by Apache ZooKeeper for heartbeats. Default: **2000**
- `ZOO_PRE_ALLOC_SIZE`': Block size for transaction log file. Default **65536**
- `ZOO_SNAPCOUNT`: The number of transactions recorded in the transaction log before a snapshot can be taken (and the transaction log rolled). Default **100000**
- `ZOO_PRE_ALLOC_SIZE`': Block size for transaction log file. Default: **65536**
- `ZOO_SNAPCOUNT`: The number of transactions recorded in the transaction log before a snapshot can be taken (and the transaction log rolled). Default: **100000**
- `ZOO_INIT_LIMIT`: Apache ZooKeeper uses to limit the length of time the Apache ZooKeeper servers in quorum have to connect to a leader. Default: **10**
- `ZOO_SYNC_LIMIT`: How far out of date a server can be from a leader. Default: **5**
- `ZOO_MAX_CNXNS`: Limits the total number of concurrent connections that can be made to a Apache ZooKeeper server. Setting it to 0 entirely removes the limit. Default: **0**
- `ZOO_MAX_CLIENT_CNXNS`: Limits the number of concurrent connections that a single client may make to a single member of the Apache ZooKeeper ensemble. Default **60**
- `ZOO_4LW_COMMANDS_WHITELIST`: List of whitelisted [4LW](https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_4lw) commands. Default **srvr, mntr**
- `ZOO_SERVERS`: Comma, space or semi-colon separated list of servers. Example: zoo1:2888:3888,zoo2:2888:3888 or if specifying server IDs zoo1:2888:3888::1,zoo2:2888:3888::2. No defaults.
- `ZOO_MAX_CLIENT_CNXNS`: Limits the number of concurrent connections that a single client may make to a single member of the Apache ZooKeeper ensemble. Default: **60**
- `ZOO_4LW_COMMANDS_WHITELIST`: List of whitelisted [4LW](https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_4lw) commands. Default: **srvr, mntr**
- `ZOO_SERVERS`: Comma, space or semi-colon separated list of servers. Example: zoo1:2888:3888,zoo2:2888:3888 or if specifying server IDs zoo1:2888:3888::1,zoo2:2888:3888::2. Default: No defaults.
- `ZOO_CLIENT_USER`: User that will use Apache ZooKeeper clients to auth. Default: No defaults.
- `ZOO_CLIENT_PASSWORD`: Password that will use Apache ZooKeeper clients to auth. No defaults.
- `ZOO_CLIENT_PASSWORD_FILE`: Absolute path to a file that contains the password that will be used by Apache ZooKeeper clients to perform authentication. No defaults.
- `ZOO_SERVER_USERS`: Comma, semicolon or whitespace separated list of user to be created. Example: user1,user2,admin. No defaults
- `ZOO_SERVER_PASSWORDS`: Comma, semicolon or whitespace separated list of passwords to assign to users when created. Example: pass4user1, pass4user2, pass4admin. No defaults
- `ZOO_SERVER_PASSWORDS_FILE`: Absolute path to a file that contains a comma, semicolon or whitespace separated list of passwords to assign to users when created. Example: pass4user1, pass4user2, pass4admin. No defaults
- `ZOO_CLIENT_PASSWORD`: Password that will use Apache ZooKeeper clients to auth. Default: No defaults.
- `ZOO_CLIENT_PASSWORD_FILE`: Absolute path to a file that contains the password that will be used by Apache ZooKeeper clients to perform authentication. Default: No defaults.
- `ZOO_SERVER_USERS`: Comma, semicolon or whitespace separated list of user to be created. Example: user1,user2,admin. Default: No defaults
- `ZOO_SERVER_PASSWORDS`: Comma, semicolon or whitespace separated list of passwords to assign to users when created. Example: pass4user1, pass4user2, pass4admin. Default: No defaults
- `ZOO_SERVER_PASSWORDS_FILE`: Absolute path to a file that contains a comma, semicolon or whitespace separated list of passwords to assign to users when created. Example: pass4user1, pass4user2, pass4admin. Default: No defaults
- `ZOO_ENABLE_AUTH`: Enable Apache ZooKeeper auth. It uses SASL/Digest-MD5. Default: **no**
- `ZOO_RECONFIG_ENABLED`: Enable Apache ZooKeeper Dynamic Reconfiguration. Default: **no**
- `ZOO_LISTEN_ALLIPS_ENABLED`: Listen for connections from its peers on all available IP addresses. Default: **no**
@@ -206,19 +206,19 @@ The configuration can easily be setup with the Bitnami Apache ZooKeeper Docker i
- `ZOO_PROMETHEUS_METRICS_PORT_NUMBER`: Port where a Jetty server will expose Prometheus metrics. Default: **7000**
- `ALLOW_ANONYMOUS_LOGIN`: If set to true, Allow to accept connections from unauthenticated users. Default: **no**
- `ZOO_LOG_LEVEL`: Apache ZooKeeper log level. Available levels are: `ALL`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL`, `OFF`, `TRACE`. Default: **INFO**
- `JVMFLAGS`: Default JVMFLAGS for the Apache ZooKeeper process. No defaults
- `JVMFLAGS`: Default JVMFLAGS for the Apache ZooKeeper process. Default: No defaults
- `ZOO_TLS_CLIENT_ENABLE`: Enable tls for client communication. Default: **false**
- `ZOO_TLS_PORT_NUMBER`: Zookeeper TLS port. Default: 3181
- `ZOO_TLS_CLIENT_KEYSTORE_FILE`: KeyStore file: Default: No Defaults
- `ZOO_TLS_CLIENT_KEYSTORE_PASSWORD`: KeyStore file password. This can be an environment variable. It will be evaluated by bash. No Defaults
- `ZOO_TLS_CLIENT_KEYSTORE_PASSWORD`: KeyStore file password. This can be an environment variable. It will be evaluated by bash. Default: No Defaults
- `ZOO_TLS_CLIENT_TRUSTSTORE_FILE`: TrustStore file: Default: No Defaults
- `ZOO_TLS_CLIENT_TRUSTSTORE_PASSWORD`: TrustStore file password. This can be an environment variable. It will be evaluated by bash. No Defaults
- `ZOO_TLS_CLIENT_TRUSTSTORE_PASSWORD`: TrustStore file password. This can be an environment variable. It will be evaluated by bash. Default: No Defaults
- `ZOO_TLS_CLIENT_AUTH`: Specifies options to authenticate TLS connections from clients. Available values are: `none`, `want`, `need`. Default: **need**
- `ZOO_TLS_QUORUM_ENABLE`: Enable tls for quorum communication. Default: **false**
- `ZOO_TLS_QUORUM_KEYSTORE_FILE`: KeyStore file: Default: No Defaults
- `ZOO_TLS_QUORUM_KEYSTORE_PASSWORD`: KeyStore file password. This can be an environment variable. It will be evaluated by bash. No Defaults
- `ZOO_TLS_QUORUM_KEYSTORE_PASSWORD`: KeyStore file password. This can be an environment variable. It will be evaluated by bash. Default: No Defaults
- `ZOO_TLS_QUORUM_TRUSTSTORE_FILE`: TrustStore file: Default: No Defaults
- `ZOO_TLS_QUORUM_TRUSTSTORE_PASSWORD`: TrustStore file password. This can be an environment variable. It will be evaluated by bash. No Defaults
- `ZOO_TLS_QUORUM_TRUSTSTORE_PASSWORD`: TrustStore file password. This can be an environment variable. It will be evaluated by bash. Default: No Defaults
- `ZOO_TLS_QUORUM_CLIENT_AUTH`: Specifies options to authenticate TLS connections from clients. Available values are: `none`, `want`, `need`. Default: **need**
- `ZOO_ENABLE_ADMIN_SERVER`: Enable [admin server](https://zookeeper.apache.org/doc/r3.5.7/zookeeperAdmin.html#sc_adminserver). Default: **yes**
- `ZOO_ADMIN_SERVER_PORT_NUMBER`: [Admin server](https://zookeeper.apache.org/doc/r3.5.7/zookeeperAdmin.html#sc_adminserver) port. Default: **8080**
@@ -332,8 +332,8 @@ A Apache ZooKeeper (https://zookeeper.apache.org/doc/r3.1.2/zookeeperAdmin.html)
- `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
- with Server ID - zoo1:2888:3888::1,zoo2:2888:3888::2
- without Server ID And Observers - zoo1:2888:3888,zoo2:2888:3888:observer
- with Server ID And Observers - zoo1:2888:3888::1,zoo2:2888:3888:observer::2
- without Server ID and Observers - zoo1:2888:3888,zoo2:2888:3888:observer
- with Server ID and Observers - zoo1:2888:3888::1,zoo2:2888:3888:observer::2
For reliable Apache ZooKeeper service, you should deploy Apache ZooKeeper in a cluster known as an ensemble. As long as a majority of the ensemble are up, the service will be available. Because Apache ZooKeeper requires a majority, it is best to use an odd number of machines. For example, with four machines Apache ZooKeeper can only handle the failure of a single machine; if two machines fail, the remaining two machines do not constitute a majority. However, with five machines Apache ZooKeeper can handle the failure of two machines.