-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] Opensearch worker unable to start in docker: SIGILL #16761
Comments
Possibly related: corretto-21/issues/85 |
That looks related, yes. I'm on |
I've tried to apply This is the command I tried: docker run -it \
-e "DISABLE_SECURITY_PLUGIN=true" \
-e "discovery.type=single-node" \
-e "OPENSEARCH_JAVA_OPTS=-XX:UseSVE=0" \
opensearchproject/opensearch:latest |
Found the same issue on my M4 Mac with 15.2, and tried the It looks like there's a Java program "org.opensearch.tools.java_version_checker.JavaVersionChecker" which is being run during image startup, but without "OPENSEARCH_JAVA_OPTS" or "JAVA_OPTS" in the command line. So it runs Java without the "-XX:UseSVE=0" prop for that program call, causing the docker image to fail with a SIGILL and therefore the image fails to load. It traces back to this bug: https://bugs.openjdk.org/browse/JDK-8345296 in the JDK. JavaVersionChecker and all java calls during image startup probably need to be examined to see if they can take in either JAVA_OPTS or OPENSEARCH_JAVA_OPTS so anyone running a M4 Mac with 15.2 can add the prop and get around this. Or the latest version of the docker image needs to be updated with a newer version of OpenJDK to take in the fix. |
same issue. any workaround ? |
Not sure why, but I was able to get this working with an m4 on os 15.2 using |
Describe the bug
I'm having an issue starting a new opensearch instance in docker locally. I'm on a brand new Macbook M4 pro. This error shows up using the default docker virtualization settings, I've tried using Docker VVM and toggling Rosetta virtualization but that didn't help. I suspect this might be a docker specific issue because I am able to get Opensearch running using the arm binary natively outside of docker. I'm also not able to repro this issue on a M2 Macbook Air.
Command:
Stack trace:
uname -a
I do not have issues starting the opensearch dashboard in a separate container.
I'm not really sure how to go about tracking this down, any help would be appreciated. Let me know what additional info I can provide.
Related component
Build
To Reproduce
Expected behavior
Opensearch server/worker start successfully.
Additional Details
Plugins
Defaults
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: