-
Notifications
You must be signed in to change notification settings - Fork 909
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
Cannot start docker #175
Comments
Yes, if a bootstrap check fails then Elasticsearch will not start. |
As mentioned at the beginning I am hosting it on my QNap, using some strange Linux version and I failed to fix the above even though I have tried a couple of tutorials. Maybe, you could think of using those as a warning instead. |
Sorry, I'm unfamiliar with QNap so can't help you work out how to set those parameters. As far as I can see, the solution from https://github.com/deviantony/docker-elk is configured to run in development mode (https://github.com/deviantony/docker-elk/blob/master/elasticsearch/config/elasticsearch.yml#L13-L16), which disables the bootstrap tests. (In production mode, Elasticsearch enforces the tests and generates the error — not the image, so I can't do anything about that like issuing a warning.) I can only see two ways of making progress here:
Hope that helps. |
Thanks for checking for the differences! Please leave the issue open for the time being. I will update it if I manage to solve those issues and I will try to rerun the docker. |
Sure thing, leaving open for now. |
Managed to solve it 👍 !! max virtual memory areas vm.max_map_count [65535] is too low
Source:
max file descriptors [4096] is too low
Source: |
About the second one... Could we modify the container file to apply those settings by default? |
Thanks for the update!
Unfortunately no, it isn't an image-specific parameter so it can only be set at runtime on the host. |
perfect. well. lets close that one. hope others will benefit. |
I am actually trying to start it on my QNap inside Container Station and it fails on me:
The only thing I could see is:
But is it something that could fail the initialization?
The text was updated successfully, but these errors were encountered: