# "Device or resource busy" when adding to keystore in Docker Compose

**URL:** <https://discuss.elastic.co/t/device-or-resource-busy-when-adding-to-keystore-in-docker-compose/228130>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [April 15, 2020, 12:59pm UTC](https://discuss.elastic.co/t/device-or-resource-busy-when-adding-to-keystore-in-docker-compose/228130 "2020-04-15T12:59:18Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![slhck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/slhck/32/32578_2.png) [@slhck](https://discuss.elastic.co/u/slhck)\
**Post date:** [May 8, 2020, 6:21pm UTC](https://discuss.elastic.co/t/device-or-resource-busy-when-adding-to-keystore-in-docker-compose/228130/3 "2020-05-08T18:21:44Z")

</div>

No solution so far. I think the fundamental issue is that the config should not live in the same directory with system generated files...

---

_[View the full topic](https://discuss.elastic.co/t/device-or-resource-busy-when-adding-to-keystore-in-docker-compose/228130)._