bbvalabs/zookeeper under the directory $ZOO_HOME.
Besides, we've added two scripts :
By default the entrypoint of container is zk_env.sh.
This image hasn't any CMD entry, users are the responsible for launching any command when they are going to run the container.
Let's run a zookeeper container :
bashdocker run -it -e "SETUP_DEBUG=true" engapa/zookeeper:${ZOO_VERSION}
NOTE: We've pass a SETUP_DEBUG environment variable to view the setup process of config files.
Users can pass parameters to config files just adding environment variables with specific name patterns.
This table collects the patterns of variable names which will are written in each file:
| PREFIX | FILE (${ZOO_HOME}/config) | Example |
|---|---|---|
| ZK_ | zoo.cfg | ZK_maxClientCnxns=0 --> maxClientCnxns=0 |
| LOG4J_ | log4j.properties | LOG4J_log4j_rootLogger=INFO, stdout--> log4j.rootLogger=INFO, stdout |
| JAVA_ZK_ | java.env | JAVA_ZK_JVMFLAG="-Xmx1G -Xms1G" --> JVMFLAG="-Xmx1G -Xms1G" |
So we can configure our zookeeper server in docker run time :
bash$docker run -it -d -e "LOG4J_log4j_rootLogger=DEBUG, stdout"
Also you may use --env-file option to load these variables from a file.
And , of course, you could provide your own properties files directly by option -v and don't use zk_setup script.
In k8s directory directory there are some resources for Kubernetes
Thanks to kubernetes team for the contrib .
In openshift directory we have a couple of templates to install within Openshift
Enrique Garcia *******


manifest unknown 错误
TLS 证书验证失败
DNS 解析超时
410 错误:版本过低
402 错误:流量耗尽
身份认证失败错误
429 限流错误
凭证保存错误
来自真实用户的反馈,见证轩辕镜像的优质服务