# Docker volume mount point

**URL:** <https://forum.inductiveautomation.com/t/docker-volume-mount-point/102490>\
**Category:** Ignition\
**Created:** [February 18, 2025, 2:29pm UTC](https://forum.inductiveautomation.com/t/docker-volume-mount-point/102490 "2025-02-18T14:29:53Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [February 19, 2025, 11:50pm UTC](https://forum.inductiveautomation.com/t/docker-volume-mount-point/102490/4 "2025-02-19T23:50:53Z")

</div>

> [@Darren\_Steele](#):
>
> I just did a quick test of mounting our volume at:
> 
> volumes:
> 
> - ignition-data:/usr/local/bin/ignition
> 
> and all seems to work.

> [@pturmel](#):
>
> making another volume and mount point for `user-lib`

Refrain from doing either of these, as you'll end up persisting built-in modules (under `user-lib/modules`) and cause yourself troubles when you want to upgrade your Docker image (and you launch the newer base platform against [persisted] older modules).

@Darren_Steele, what kind of data are you storing there? If you're loading custom pylib content, take a look at the post [here](https://forum.inductiveautomation.com/t/bind-mount-the-pylib-on-docker-container/86052/2).

---

_[View the full topic](https://forum.inductiveautomation.com/t/docker-volume-mount-point/102490)._