Public | Automated Build

Last pushed: 2 years ago
Short Description
Short description is empty for this repo.
Full Description


This Docker image contains Zookeeper 3.5.1-rc2 which features dynamic host reconfiguration. Upon start, it attempts to join an existing cluster.

The syntax to start a container is like this:

docker run --net host --name [name] containersol/zookeeper [id] [ip]


  • id = id of the zookeeper node (known internally as myid)
  • ip = ip address of a node of the existing cluster

The id is mandatory, the ip is optional.

The --net host is needed for zookeepers on different hosts to be able to contact each other.

Docker Pull Command
Source Repository

Comments (2)
a year ago

Is this still being supported by you guys?

I am trying to run a 3 node zookeeper cluster on 3 coreos nodes in openstack, first unit comes up fine with
usr/bin/docker run --net=host --name zk1 containersol/zookeeper

however 2nd and 3rd do not initialize properly throwing the below error
Jul 07 20:26:35 systemd[1]: Started docker container 7ef493984bfe5028bb528bb434a7ca4c3ca1041de473117380d297224117f67b.
Jul 07 20:26:36 docker[1734]: /usr/local/bin/ line 38: output: command not found
Jul 07 20:26:36 docker[1734]: /usr/local/bin/ line 25: sorted_id_list: bad array subscript
Jul 07 20:26:36 docker[1734]: /usr/bin/java
Jul 07 20:26:36 docker[1734]: Force enabled, data/txnlog directories will be re-initialized
Jul 07 20:26:36 docker[1734]: Using myid of 1
Jul 07 20:26:36 docker[1734]: ZooKeeper JMX enabled by default
Jul 07 20:26:36 docker[1734]: /usr/bin/java
Jul 07 20:26:36 docker[1734]: Using config: /tmp/zookeeper/bin/../conf/zoo.cfg
Jul 07 20:26:37 docker[1734]: Starting zookeeper ... FAILED TO START

seems there is some issue in the zkinit getting myid ?

I can provide more complet journalctl logs if needed


2 years ago

Looks like there is a bad configuration file

2016-02-15 19:30:29,223 [myid:] - ERROR [main:QuorumPeerMain@86] - Invalid config, exiting abnormally