-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
"Too many open files" exception when running from Docker #18022
Comments
The problem is your max file descriptors are too low. There's even a warning in your logs:
|
Im running elasticsearch from the official docker image: https://hub.docker.com/_/elasticsearch/ On my host environment, both hard and soft limits are greater than 65536:
However inside the container:
|
There is not an official Docker image that is affiliated with Elastic. To be clear, the "official" Docker image on Docker Hub is not affiliated with Elastic. |
I would never have thought that... Already submitted to docker-library/elasticsearch#102 thank you! |
Fixed! If anyone has the same problem, try running the container with
|
there is still same problem, when I use docker stack deploy -c in swarm @fauria |
how do i do this with docker-compose? |
Hi @chovy, I know it's probably too late, but the official docs on docker-compose files say it's pretty straightforward:
This should be done in your desired service's section. |
Elasticsearch version: 2.3.2 (Dockerfile elasticsearch:latest)
JVM version: openjdk version "1.8.0_72-internal"
OS version: Docker image: https://hub.docker.com/_/elasticsearch/
Description of the problem including expected versus actual behavior:
Expected behavior: An elasticsearch docker container successfully started.
Actual behavior: An elasticsearch docker container fails to start.
Steps to reproduce:
docker pull elasticsearch
docker run -i -t --rm -v /srv/elasticseach/data:/usr/share/elasticsearch/data -v /srv/elasticseach/config:/usr/share/elasticsearch/config elasticsearch
Provide logs (if relevant):
http://pastebin.com/raw/kf0LDGxD
The text was updated successfully, but these errors were encountered: