@infodog nice catch. I think the problem is related to #1601 . in 3.4.13, zookeeper cli always returns '0' as return code, which cause the docker image skip initializing cluster. zookeeper commit: fade262a8a4fa744bd768dc7569d8f4c9d84f275 and issue [ZOOKEEPER-1898](https://issues.apache.org/jira/browse/ZOOKEEPER-1898).
the problem will only be caught when a cluster is never initialized by the bookkeeper shell script before. will see how to fix it (or work around in the docker image) and add a test case to cover this case. [ Full content available at: https://github.com/apache/bookkeeper/pull/1644 ] This message was relayed via gitbox.apache.org for [email protected]
