-
Notifications
You must be signed in to change notification settings - Fork 686
Master node errors #198
Comments
The issue is not with my environment as I'm able to build cluster with different configs. Wondering if there is issue in new 6.3.0 image? |
@pires I believe 6.3.0 is broken. ES appears to be attempting to run Running an ldd on this binary shows that there are issues with missing shared libraries and missing symbols (alpine?):
|
The relevant ES code seems to be here: It appears to attempt to spawn native controllers based on whether they exist in the filesystem. Adding the following to
|
if running on k8s, how can run.sh be modified? Is quay.io/pires/elasticsearch:6.2.4 image still compatible? |
@rocketraman I think you may have run one image that was pushed erroneously. Can you make sure you are downloading the current 6.3.0 tag? I just brought a new Kubernetes cluster up and was able to run everything as expected. |
@pires I believe I have the latest image. Here is the docker history:
And this is the error I get on startup, without the workaround I posted above, which causes the image to crash loop:
@rewt If you're getting the same error as me, you can build an image that extends
and build / push it:
|
The right tag is |
Please, delete the image from your system and pull again. |
@pires It's the right one - the sha256 digest starts with
|
Digging deeper into errors, I found my issue documented here #64 Adding |
@rewt Thanks, I'll create another issue for what I was seeing as it looks to be a different problem. |
The text was updated successfully, but these errors were encountered: