-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[bitnami/zookeeper] zookeeper arm64 docker images(3.9.x) in hub.docker.com is invalid! #68070
Comments
Hi @zhengchaoken, Thanks for using Bitnami. We have not being able to reproduce your issue with the same 3.9.1 image you mentioned. We started with an empty volume, started the container, stopped it, and then started it again without issues (we also see the I also see in dockerhub that the most recent image for the 3.9.1 version is from 4 months ago. Do you also reproduce your issue with the latest 3.9.2 version? Can it be related somehow to the persisted data you are using? |
I have tried both 3.9.1 & 3.9.2 start docker common was can you provide your docker pulll command , docker run command and linux ‘uname -a ’ result I will try your commonds and check my useage to find the problem Thanks very much ! |
Hi @zhengchaoken, We used the commands you shared on your first post to pull the Zookeeper image and to run it with a mounted volume. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/zookeeper:3.9.x
What architecture are you using?
arm64
What steps will reproduce the bug?
environment: aarch64 GNU/Linux
step 1. pull arm image and load
step 2. startup
step 3. check
check log
however QuorumPeerMain is in the file , usr jar tf to check
docker build check
What is the expected behavior?
What do you see instead?
Additional information
The text was updated successfully, but these errors were encountered: