-
Notifications
You must be signed in to change notification settings - Fork 273
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]: Misleading error on old docker version (19), node segfaults #4088
Comments
Hi @maaaax, pls let us know if you are still facing the issue or it's resolved. Thanks |
Hi, I have updated docker to >19 and everything works fine with that. So, for me not a problem. But maybe the start scripts should not write something about missing binaries (node,java) when they are actually just segfaulting. |
[Untriage] Adding @peterzhuamazon @gaiksaya @bbarani should this be moved to OpenSearch Dashboards repo? |
Yeah makes sense. If the docker image or any path needs to change in order to resolve this I believe dashboards team would be able to point it out. |
@AMoo-Miki @joshuarrrr @kavilla @ashwin-pc Can you please provide your inputs here? |
Will need to recreate this on my own to figure what is wrong. I am not sure why OpenSearch wouldn't work though. |
Seems both are not working:
|
2.9.0 works within the same setup:
|
I think it's solved.
this, by googling, led me to adding "--security-opt seccomp=unconfined" to docker run. java, node 14 and 18 are working with that option! |
Hi, @maaaax , happy to learn that you have found the way out on this issue.
|
Describe the bug
At least with 19.03.13 opensearch and dashboards 2.10.0 containers are unable to start.
Dashboards exits with
"Could not find a Node.js runtime binary bundled with OpenSearch Dashboards or on the system" (bin/use_node)
Actually node is segfaulting (nodejs/node#43064)
ulimits have been set, but no effect.
starts:
docker run -it opensearchproject/opensearch-dashboards:2.9.0
doesn't start:
docker run -it opensearchproject/opensearch-dashboards:2.10.0
Furthermore, opensearch container exits with java not found in JAVA_HOME. I haven't looked into this, just upgraded docker to get it working.
To reproduce
Install
Client: Docker Engine - Community
Version: 19.03.13
API version: 1.40
Go version: go1.13.15
Git commit: 4484c46d9d
Built: Wed Sep 16 17:03:45 2020
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.13
API version: 1.40 (minimum version 1.12)
Go version: go1.13.15
Git commit: 4484c46d9d
Built: Wed Sep 16 17:02:21 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.3.7
GitCommit: 8fba4e9a7d01810a393d5d25a3621dc101981175
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Try to run opensearch.
Expected behavior
Print some error message that the binary exists but fails to start.
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: