-
-
Notifications
You must be signed in to change notification settings - Fork 656
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
Version 0.22.0 Docker image broken, "insufficient memory for the Java Runtime Environment" #1199
Comments
Hello! We are facing the same issue here. We have three clusters and two of them work fine after upgrading to 0.22.0, but the third one is throwing exactly the same error message. The only difference I can see is that the one where it is not working is a RedHat 8.5 VM while the other two are on RedHat 8.6. The strange thing is that the VM where it is not working has 32GB RAM while the other two only have 16GB RAM. And there is more free RAM available on the machine with 32GB where it is not working. Any idea why this happens? Kind regards Jens |
The container start and the ui is reachable or don't start at all ? |
To me it looks like it doesn't even start the JVM. This is the difference between a working instance and a failing instance: Failing:
Working:
|
I cannot even run
|
what is the os that is running docker? |
It is RedHat on both. The one that is working is on RedHat 8.6, the one that is NOT working is on RedHat 8.5. Both have a different docker version:
|
I just found this. Are you using |
If I understand here, it's Just confirmed inside the container
|
Hello @erkexzcx ! Were you able to make any progress on this issue? Thanks and kind regards Jens |
Would it be possible to provide an AKQ image based on the KR |
Yes.,? I downgraded docker image from |
This works for me as well, but I'd like to have the features of 0.22.0. That's why I would like to get this issue solved. Best regards |
You could easily built it locally and see if the issue is resolved or not ? It's clearly not the goal to use old version instead of new one, I would prefer understand the issue and fix it but I'm not able to reproduce it at all. |
I'm experiencing similar issues with the 0.22.0 image on Debian 10 with docker version 18.09.5
|
Same issue on Ubuntu 20 with version 0.22.0 :
|
Hi, it seems to be a problem with the docker version. I can confirm for RedHat that it works on RedHat 8.6 with a newer docker version than on RedHat 8.5. Please see this comment for details. Cheers Jens |
The issue is on docker side and I can't do anything. |
Version
0.21.0
is working fine, but it's broken on0.22.0
.This is what I am getting when opening
docker logs -f akhq
Other notes that might help:
bootstrap.servers
field is specified).The text was updated successfully, but these errors were encountered: