# Docker error during 3-node cluster running **URL:** \ **Category:** Elasticsearch\ **Tags:** docker\ **Created:** [September 27, 2022, 6:51pm UTC](https://discuss.elastic.co/t/docker-error-during-3-node-cluster-running/315304 "2022-09-27T18:51:26Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tifty](https://avatars.discourse-cdn.com/v4/letter/t/eb9ed0/32.png) [@tifty](https://discuss.elastic.co/u/tifty)\ **Post date:** [September 27, 2022, 6:51pm UTC](https://discuss.elastic.co/t/docker-error-during-3-node-cluster-running/315304/1 "2022-09-27T18:51:26Z")
Hi everyone, I am trying to run a 3-node cluster on my local machine. Although it doesn't happen with every run but at times I am getting the "Error response from daemon: i/o timeout" error in one of the nodes randomly and the service shuts down. I have looked in other online discussion forums for possible solutions but still couldn't find a solid resolve for this. Can anyone suggest me any possible ways to harden my deployment? ![Capture](https://us1.discourse-cdn.com/elastic/original/3X/b/3/b30837afdbe75e5c0b0fce7e8994d6bf049a3691.png) ---
**Author:** ![matschaffer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matschaffer/32/95396_2.png) [@matschaffer](https://discuss.elastic.co/u/matschaffer)\ **Post date:** [October 13, 2022, 6:57am UTC](https://discuss.elastic.co/t/docker-error-during-3-node-cluster-running/315304/2 "2022-10-13T06:57:35Z")
This is a docker-level error, I believe coming from [moby/request.go at a98bd75256122a3e386059e1a6336ee6b82aed62 · moby/moby · GitHub](https://github.com/moby/moby/blob/a98bd75256122a3e386059e1a6336ee6b82aed62/client/request.go#L242) I'd check for connection issues between your docker cli (looks like probably docker compose) and your docker server. An i/o timeout could mean the docker server isn't responding or is responding too slowly. Folks on [https://forums.docker.com/](https://forums.docker.com/) might also have some ideas of how to troubleshoot. ---
**Author:** ![tifty](https://avatars.discourse-cdn.com/v4/letter/t/eb9ed0/32.png) [@tifty](https://discuss.elastic.co/u/tifty)\ **Post date:** [October 18, 2022, 8:24pm UTC](https://discuss.elastic.co/t/docker-error-during-3-node-cluster-running/315304/3 "2022-10-18T20:24:16Z")
Hi @matschaffer, Yes, I was able to solve the issue by setting the vm.max\_map\_count parameter for the system. This post [elasticsearch - How to increase vm.max\_map\_count? - Stack Overflow](https://stackoverflow.com/questions/42889241/how-to-increase-vm-max-map-count) helped me. ---
**Author:** ![matschaffer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matschaffer/32/95396_2.png) [@matschaffer](https://discuss.elastic.co/u/matschaffer)\ **Post date:** [October 19, 2022, 1:24am UTC](https://discuss.elastic.co/t/docker-error-during-3-node-cluster-running/315304/4 "2022-10-19T01:24:03Z")
Interesting! Usually I see the max\_map\_count issue surface in the ES output rather than the docker response. For example: ```auto $ docker run --rm -it docker.elastic.co/elasticsearch/elasticsearch:8.4.3 [snip] {"@timestamp":"2022-10-19T01:22:43.426Z", "log.level": "INFO", "message":"bound or publishing to a non-loopback address, enforcing bootstrap checks", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.BootstrapChecks","elasticsearch.node.name":"ceb02e219d5e","elasticsearch.cluster.name":"docker-cluster"} bootstrap check failure [1] of [1]: max virtual memory areas vm.max_map_count [65535] is too low, increase to at least [262144] ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/docker-cluster.log {"@timestamp":"2022-10-19T01:22:43.433Z", "log.level": "INFO", "message":"stopping ...", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"Thread-0","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"ceb02e219d5e","elasticsearch.cluster.name":"docker-cluster"} {"@timestamp":"2022-10-19T01:22:43.472Z", "log.level": "INFO", "message":"stopped", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"Thread-0","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"ceb02e219d5e","elasticsearch.cluster.name":"docker-cluster"} {"@timestamp":"2022-10-19T01:22:43.473Z", "log.level": "INFO", "message":"closing ...", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"Thread-0","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"ceb02e219d5e","elasticsearch.cluster.name":"docker-cluster"} {"@timestamp":"2022-10-19T01:22:43.481Z", "log.level": "INFO", "message":"closed", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"Thread-0","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"ceb02e219d5e","elasticsearch.cluster.name":"docker-cluster"} {"@timestamp":"2022-10-19T01:22:43.483Z", "log.level": "INFO", "message":"Native controller process has stopped - no new native processes can be started", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"ml-cpp-log-tail-thread","log.logger":"org.elasticsearch.xpack.ml.process.NativeController","elasticsearch.node.name":"ceb02e219d5e","elasticsearch.cluster.name":"docker-cluster"} ERROR: [1] bootstrap checks failed. You must address the points described in the following [1] lines before starting Elasticsearch. ``` Glad you found it though! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 16, 2022, 1:24am UTC](https://discuss.elastic.co/t/docker-error-during-3-node-cluster-running/315304/5 "2022-11-16T01:24:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.