# Root user in ES 2.4 in Docker container
**URL:** https://discuss.elastic.co/t/root-user-in-es-2-4-in-docker-container/61677
**Category:** Elasticsearch
**Created:** [September 28, 2016, 9:07am UTC](https://discuss.elastic.co/t/root-user-in-es-2-4-in-docker-container/61677 "2016-09-28T09:07:31Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@vvs14](https://discuss.elastic.co/u/vvs14)
#### Post date: [September 28, 2016, 9:07am UTC](https://discuss.elastic.co/t/root-user-in-es-2-4-in-docker-container/61677/1 "2016-09-28T09:07:31Z")
I am running ELK stack with Docker for log management with current configuration of ES 1.7, Logstash 1.5.4 and Kibana 4.1.4. Now I am trying to upgrade Elasticsearch to 2,4 by using tar.gz file with Docker. As ES 2.X, does not allow running it as root user, I have used `-Des.insecure.allow.root=true` option while running the elasticsearch service, yet my container don't start. The logs don't mention any problem.
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 100 874 100 874 0 0 874k 0 --:--:-- --:--:-- --:--:-- 853k
> //opt//log-management//elasticsearch/bin/elasticsearch: line 134: hostname: command not found
> > Scheduler@0.0.0 start /opt/log-management/Scheduler
> > node scheduler-app.js
> > ESExportWrapper@0.0.0 start /opt/log-management/ESExportWrapper
> > node app.js
> Jobs are registered
> [2016-09-28 09:04:24,646][INFO][bootstrap] max\_open\_files [1048576]
> [2016-09-28 09:04:24,686][WARN][bootstrap] running as ROOT user. this is a bad idea!
> Native thread-sleep not available.
> This will result in much slower performance, but it will still work.
> You should re-install spawn-sync or upgrade to the lastest version of node if possible.
> Check /opt/log-management/ESExportWrapper/node\_modules/sync-request/node\_modules/spawn-sync/error.log for more details
> [2016-09-28 09:04:24,874][INFO][node] [Kismet Deadly] version[2.4.0], pid[1], build[ce9f0c7/2016-08-29T09:14:17Z]
> [2016-09-28 09:04:24,874][INFO][node] [Kismet Deadly] initializing ...
> Wed, 28 Sep 2016 09:04:24 GMT express deprecated app.configure: Check app.get('env') in an if statement at lib/express/index.js:60:5
> Wed, 28 Sep 2016 09:04:24 GMT connect deprecated multipart: use parser (multiparty, busboy, formidable) npm module instead at node\_modules/express/node\_modules/connect/lib/middleware/bodyParser.js:56:20
> Wed, 28 Sep 2016 09:04:24 GMT connect deprecated limit: Restrict request size at location of read at node\_modules/express/node\_modules/connect/lib/middleware/multipart.js:86:15
> [2016-09-28 09:04:25,399][INFO][plugins] [Kismet Deadly] modules [reindex, lang-expression, lang-groovy], plugins , sites
> [2016-09-28 09:04:25,423][INFO][env] [Kismet Deadly] using [1] data paths, mounts [[/data (/dev/mapper/platform-data)]], net usable\_space [1tb], net total\_space [1tb], spins? [possibly], types [xfs]
> [2016-09-28 09:04:25,423][INFO][env] [Kismet Deadly] heap size [7.8gb], compressed ordinary object pointers [true]
> [2016-09-28 09:04:25,455][WARN][threadpool] [Kismet Deadly] requested thread pool size [60] for [index] is too large; setting to maximum [24] instead
> [2016-09-28 09:04:27,575][INFO][node] [Kismet Deadly] initialized
> [2016-09-28 09:04:27,575][INFO][node] [Kismet Deadly] starting ...
> [2016-09-28 09:04:27,695][INFO][transport] [Kismet Deadly] publish\_address {10.240.118.68:9300}, bound\_addresses {[::1]:9300}, {127.0.0.1:9300}
> [2016-09-28 09:04:27,700][INFO][discovery] [Kismet Deadly] ccs-elasticsearch/q2Sv4FUFROGIdIWJrNENVA
Any leads would be appreciated.
Stackoverflow link with more information: [http://stackoverflow.com/questions/39768453/root-user-in-elasticsearch-2-4-in-docker-container](http://stackoverflow.com/questions/39768453/root-user-in-elasticsearch-2-4-in-docker-container)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:15pm UTC](https://discuss.elastic.co/t/root-user-in-es-2-4-in-docker-container/61677/2 "2017-07-05T22:15:51Z")