-
Notifications
You must be signed in to change notification settings - Fork 173
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
latest docker image crashes on MacM4 (prob due to JDK bump) #551
Comments
@tombrus I think you might be hitting this bug in eclipse temurin 21: adoptium/adoptium-support#1223 To apply their workaround, can you try adding
Does neo4j start? |
Hi @jennyowen, thanks for looking into this. Unfortunately neo4j does not start (the container keeps restarting):
I don't think it is relevant, but I ran it with docker compose:
|
OK interesting. So what happens if you don't set |
then it is still restarting but without the SIGILL:
|
Restarting? So Neo4j still isn't starting? What's the error message if there's no SIGILL? |
sorry, this is all the output there is....
|
when I set restart to no, the container runs once, the status is:
with output:
|
TLDR: this is a java bug and right now there is no workaround. You'll have to stick to OK so given the information here, I think this is that bug in temurin java 21. The problem is that the neo4j docker image interacts with the jdk a few times before actually starting the neo4j database:
There's currently no way for users to apply the workaround flag during either of those two steps. I think the second step doesn't even have any way of adding the extra jvm flag, so that may need a change to neo4j itself. I will need to investigate further. |
@jennyowen thanks for the analysis, I understand the situation, I'll stick to 5.26 for now and hope this will be fixed in java 21 some time in the future. I see that JDK issue 8345296 you indirectly refer to above is in state FIXED on java 24, I guess/hope it will be back ported to java 21 eventually... Thanks for looking into this @jennyowen and I hope other AppleSilicon users will find this helpful. |
Steps to reproduce
Expected behaviour
a running container
Actual behaviour
exit code = 134
Neo4j image tag being used
neo4j:latest
The output of the
docker version
commandOperating system
error messages
additional info
The following runs fine:
I noticed that in this version the JDK was bumped from 17 to 21. There might be a relation.
The text was updated successfully, but these errors were encountered: