-
Notifications
You must be signed in to change notification settings - Fork 907
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
sysctl: setting key "vm.max_map_count": Read-only file system #99
Comments
Usually the init script can't set the key (because the container can't write to a read-only file system), but that doesn't prevent Elasticsearch from starting if the host's |
Oh sure.
host: Ubuntu 16.04.1 LTS \n \l
|
Can't reproduce over here, so I'm going to attempt something based on your experience. Essentially I want to change this bit:
to check if Before I do that I need to make sure that the script will play nicely with your set-up once this test is in place, so could I ask you to edit the |
I have the same problem. |
@mrazvan92 Could you try the procedure outlined in #99 (comment) and let me know how it goes? |
Starting elkdocker_elk_1 |
@mrazvan92 You might not be having the same problem as @bezrukovp:
You may actually be running into (resolved) issue #92. |
@spujadas thanks thanks thanks :) |
i have similar problem.. |
my issue is how to increase the size of the memory... |
@thomasdola See the linked comment (#92 (comment)) in my previous reply. For more on this see https://www.elastic.co/guide/en/elasticsearch/reference/5.0/vm-max-map-count.html#vm-max-map-count (and feel free to ask for advice on the Elastic forums as this issue is non-Docker-specific). |
thanks |
Fixed by PR #106: if your |
I'm seeing this problem as well on the latest images, it's unable to start ElasticSearch after a read-only filesystem error when trying to set vm.max_map_count:
Reproduced on both latest and fresh installed CentOS and Ubuntu with the latest Docker version (1.13.1). |
@dmsimard The actual error is:
See #92 (comment) for more on how to fix this. |
@spujadas oh, I had read that but didn't realize it was on the host running the container that I had to try and run it. That fixed it for me, thanks. |
@dmsimard Oh OK, I'll emphasise that in the docs to make it clearer! Cheers. |
Just in case anyone finds this thread and is looking for how to set this variable on the host and you're running Docker on macOS, do this from terminal: docker-machine ssh |
I/O exception while trying to read [/proc/sys/vm/max_map_count] |
Guys use this command |
|
If you are on Mac using colima instead of Docker Desktop, you can do this colima ssh -- sudo sysctl -w vm.max_map_count=262144 |
Hi, I have the same problem:
It arises here
/elasticsearch-init:137
On my server Docker install in LXC container, perhaps this is the reason the error.
The text was updated successfully, but these errors were encountered: