# Es 7 and docker single node cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [April 12, 2019, 8:59am UTC](https://discuss.elastic.co/t/es-7-and-docker-single-node-cluster/176585 "2019-04-12T08:59:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jillesvangurp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jillesvangurp/32/3863_2.png) [@jillesvangurp](https://discuss.elastic.co/u/jillesvangurp)\ **Post date:** [April 12, 2019, 8:59am UTC](https://discuss.elastic.co/t/es-7-and-docker-single-node-cluster/176585/1 "2019-04-12T08:59:43Z")
I'm trying to get a single node docker node up and running for testing. It seems things have changed since 6.7 and it now aborts with a "the default discovery settings are unsuitable for production use; at least one of [discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes] must be configured" So, what's the magic docker incantation for a bog standard single node cluster intended for development? BTW. I noticed the docker image has gotten progressively more fussy about settings over the 6.x release. It seems to want all sorts of configuration; which is appropriate for production use but not for development. So, please update your documentation and error message to make it very clear how to run ES using docker for development (or as in my case, integration tests) as it currently isn't. ---
**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\ **Post date:** [April 12, 2019, 9:14am UTC](https://discuss.elastic.co/t/es-7-and-docker-single-node-cluster/176585/2 "2019-04-12T09:14:37Z")
To run the docker image in development mode, you should [set `discovery.type` to `single-node`](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#docker-cli-run-dev-mode). The `single-node` discovery type is explained [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html#single-node-discovery). > BTW. I noticed the docker image has gotten progressively more fussy about settings over the 6.x release. It seems to want all sorts of configuration; which is appropriate for production use but not for development. Not setting `single-node` discovery is probably the reason why you've run into the [bootstrap checks](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html#bootstrap-checks) on 6.x. ---
**Author:** ![jillesvangurp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jillesvangurp/32/3863_2.png) [@jillesvangurp](https://discuss.elastic.co/u/jillesvangurp)\ **Post date:** [April 12, 2019, 1:12pm UTC](https://discuss.elastic.co/t/es-7-and-docker-single-node-cluster/176585/3 "2019-04-12T13:12:59Z")
Thanks, I'd still recommend making this more obvious in the docker documentation. There is an enormous amount of documentation and literally anyone trying out Elasticsearch via docker is going to run into this. ---
**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\ **Post date:** [April 16, 2019, 7:16am UTC](https://discuss.elastic.co/t/es-7-and-docker-single-node-cluster/176585/4 "2019-04-16T07:16:56Z")
That's a good suggestion. We will look into this. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 14, 2019, 7:17am UTC](https://discuss.elastic.co/t/es-7-and-docker-single-node-cluster/176585/5 "2019-05-14T07:17:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.