# Switch to Official 5.1.1 Docker Image Node Lock

**URL:** <https://discuss.elastic.co/t/switch-to-official-5-1-1-docker-image-node-lock/87930>\
**Category:** Elasticsearch\
**Created:** [June 1, 2017, 2:46pm UTC](https://discuss.elastic.co/t/switch-to-official-5-1-1-docker-image-node-lock/87930 "2017-06-01T14:46:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steven\_McCord](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@Steven\_McCord](https://discuss.elastic.co/u/Steven_McCord)\
**Post date:** [June 1, 2017, 2:46pm UTC](https://discuss.elastic.co/t/switch-to-official-5-1-1-docker-image-node-lock/87930/1 "2017-06-01T14:46:30Z")

</div>

I switched from elasticsearch:5.1.1 to the new official docker image and when I run this on a previously mounted data drive I get the following when starting it up. I noticed that it has my cluster name in the data path whereas the old version did not. In my development environment it can startup just fine without any data and it doesn't include the data path. The error is below. Any thoughts would be helpful. Thanks!

[2017-06-01T14:38:27,540][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [eazy-e-0] uncaught exception in thread [main]  
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: failed to obtain node locks, tried [[/usr/share/elasticsearch/data/icx-es-data]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max\_local\_storage\_nodes] (was [1])?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 29, 2017, 2:46pm UTC](https://discuss.elastic.co/t/switch-to-official-5-1-1-docker-image-node-lock/87930/2 "2017-06-29T14:46:46Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.