-
-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
31z4/zookeeper:latest is not 3.5 but 3.4 #82
Comments
same here using docker-compose:
runnig: image:
logs:
|
@JiniousChoi in the meantime you can set image:
|
Sorry, |
Thanks and sure thing. I forced it so :) Just letting the maintainer know what he was missing. |
@JiniousChoi since it is not maintained anymore just migrate to:
|
@eriknyk Checked. Thanks |
Before you file an issue here, please keep in mind that your issue may be not related to the image itself. Please make sure that it is, otherwise report the issue upstream.
Expected behavior
As the main README.md states at via-docker-stack-deploy-or-docker as follows
I expected for the given docker-compose.yml to work with a automatically-pulled lastest zookeeper but it turned out that those 2181 ports were missing.
I think the README.md itself is contradictory. One needs to either remove
;2181
part as in:2888:3888;2181
or removeThis will start Zookeeper 3.5 in replicated mode. Please note...
like the quote above.Actual behavior
Tell us what happens instead.
docker pull 31z4/zookeeper:latest
should fetch a version of 3.5Steps to reproduce the behavior
As you would see below the history of the zk image reveals its version as 3.4
The text was updated successfully, but these errors were encountered: