# Docker create --volume /srv - but /srv is already in use - alternatives? **URL:** \ **Category:** PMM 2.x\ **Created:** [November 29, 2021, 2:32pm UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265 "2021-11-29T14:32:37Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![lkraav](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lkraav/32/5198_2.png) [@lkraav](https://forums.percona.com/u/lkraav)\ **Post date:** [November 29, 2021, 2:32pm UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265/1 "2021-11-29T14:32:37Z")
Hi. Reading [Docker - Percona Monitoring and Management](https://www.percona.com/doc/percona-monitoring-and-management/2.x/setting-up/server/docker.html) it’s a bit unclear why `/srv` is so critical for non-data-loss upgrades? If my `/srv` is already occupied with other tasks - specifically, it has a few systemd-nspawn container sub-directories, what are my options here? ---
**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\ **Post date:** [November 30, 2021, 11:53am UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265/2 "2021-11-30T11:53:01Z")
Basically inside /srv you have all the metrics data among other things. You can map a different path if you want. Check out this article for instructions: [Using Different Mount Points on Percona Monitoring and Management 2 Docker Deployments - Percona Database Performance Blog](https://www.percona.com/blog/2020/05/18/using-different-mount-points-on-percona-monitoring-and-management-2-docker-deployments/) ---
**Author:** ![lkraav](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lkraav/32/5198_2.png) [@lkraav](https://forums.percona.com/u/lkraav)\ **Post date:** [November 30, 2021, 11:55am UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265/3 "2021-11-30T11:55:58Z")
Tyvm, didn’t think to search the blog for some reason! ---
**Author:** ![lkraav](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lkraav/32/5198_2.png) [@lkraav](https://forums.percona.com/u/lkraav)\ **Post date:** [December 1, 2021, 3:08pm UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265/4 "2021-12-01T15:08:55Z")
@Ivan_Groenewold can you still clarify for me: does this `/srv` path influence docker host directory, or does it simply live a inside a docker container? I just executed `sudo docker create --volume /opt/pmm-data --name pmm-data percona/pmm-server:2 /bin/true` and don’t see anything new created in host `/opt` directory. [docker create | Docker Documentation](https://docs.docker.com/engine/reference/commandline/create/) seems to also indicate `-v ` lives inside container, but could you confirm this for me? ---
**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\ **Post date:** [December 1, 2021, 3:11pm UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265/5 "2021-12-01T15:11:25Z")
Hello, the /srv is just inside the container… as stated in the blog post that I linked you can check the “real” directory outside the container and remap it. ---
**Author:** ![lkraav](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lkraav/32/5198_2.png) [@lkraav](https://forums.percona.com/u/lkraav)\ **Post date:** [December 2, 2021, 8:51am UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265/7 "2021-12-02T08:51:36Z")
Thanks, I will fork [GitHub - percona/pmm-doc: Percona Monitoring and Management (PMM) Technical Documentation](https://github.com/percona/pmm-doc/) and provide a PR with ideas on how to make the official instruction more clear about this. ---
**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\ **Post date:** [December 2, 2021, 12:31pm UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265/8 "2021-12-02T12:31:22Z")
Thank you for your contribution! ---
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [December 2, 2021, 2:30pm UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265/9 "2021-12-02T14:30:39Z")
Hi, it would be cool if you could contribute to the documentation. Perhaps a special section on our website can help you > **[Percona Product Documentation](https://percona.community/contribute/documentation/)** > > How to contribute to the Percona Product Documentation ---
**Author:** ![Lenz\_Grimmer](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lenz_grimmer/32/2419_2.png) [@Lenz\_Grimmer](https://forums.percona.com/u/Lenz_Grimmer)\ **Post date:** [December 2, 2021, 2:38pm UTC](https://forums.percona.com/t/docker-create-volume-srv-but-srv-is-already-in-use-alternatives/13265/10 "2021-12-02T14:38:23Z")
> [@lkraav](#): > > Thanks, I will fork [GitHub - percona/pmm-doc: Percona Monitoring and Management (PMM) Technical Documentation](https://github.com/percona/pmm-doc/) and provide a PR with ideas on how to make the official instruction more clear about this. That’d be awesome. Thank you in advance, @lkraav - let us know when you’ve submitted it (or if you need assistance with submitting the PR).