# Managing Persistent Volume Claims and UIDs with Kubernetes/Docker

**URL:** <https://discuss.elastic.co/t/managing-persistent-volume-claims-and-uids-with-kubernetes-docker/75791>\
**Category:** Elasticsearch\
**Created:** [February 20, 2017, 7:34pm UTC](https://discuss.elastic.co/t/managing-persistent-volume-claims-and-uids-with-kubernetes-docker/75791 "2017-02-20T19:34:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xrl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xrl/32/3556_2.png) [@xrl](https://discuss.elastic.co/u/xrl)\
**Post date:** [February 20, 2017, 7:34pm UTC](https://discuss.elastic.co/t/managing-persistent-volume-claims-and-uids-with-kubernetes-docker/75791/1 "2017-02-20T19:34:51Z")

</div>

I am deploying Elasticsearch 5.2.1 as a docker container, managed under kubernetes.

I use managed network storage to back all the Elasticsearch data. Kubernetes is happy to create/format/mount/remount volumes through a containers whole life cycle. With the change in 5 to always run without root, how are people managing UIDs in a distributed environment?

I am mostly unfamiliar with docker's "run as" functionality, where the docker image has a local user account and runs under that non-root account. How does that impact file ownership in the situation where a container is moved to another host?

---

<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:** [March 20, 2017, 7:35pm UTC](https://discuss.elastic.co/t/managing-persistent-volume-claims-and-uids-with-kubernetes-docker/75791/2 "2017-03-20T19:35:28Z")

</div>

Closed on March 20, 2017, 7:35pm UTC

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