# Run multiple Elasticsearch Docker containers on node
**URL:** https://discuss.elastic.co/t/run-multiple-elasticsearch-docker-containers-on-node/125395
**Category:** Elasticsearch
**Created:** [March 23, 2018, 5:02pm UTC](https://discuss.elastic.co/t/run-multiple-elasticsearch-docker-containers-on-node/125395 "2018-03-23T17:02:46Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@mpmichelsen](https://discuss.elastic.co/u/mpmichelsen)
#### Post date: [March 23, 2018, 5:02pm UTC](https://discuss.elastic.co/t/run-multiple-elasticsearch-docker-containers-on-node/125395/1 "2018-03-23T17:02:47Z")
I am new to Docker and its use with the Elastic stack.
I am looking to setup a hot/warm cluster for log collection/analysis with about 15 nodes. For compliance reasons virtualization is out and the time cost to administer these nodes is significant. Therefore, I am looking to reduce the node count, if possible, using Docker to run multiple copies of Elasticsearch on a node. Two ideas I have are:
1. Double up on the warm nodes: 1 data plus 1 master instances. In this case it might make sense to have 5 masters instead of 3. To me it solves the problem with JVM garbage collection on a data node interfering with also being a master node.
2. Double up on the warm nodes: 2 data instances. Each has it's JVM cache but share the system file cache.
Would either be workable or do I need to stay with physical nodes for each server?
Marty
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 20, 2018, 5:02pm UTC](https://discuss.elastic.co/t/run-multiple-elasticsearch-docker-containers-on-node/125395/2 "2018-04-20T17:02:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.