# Docker volume mount point **URL:** \ **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:** 6\ **Page:** 1
**Author:** ![Darren\_Steele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/darren_steele/32/55624_2.png) [@Darren\_Steele](https://forum.inductiveautomation.com/u/Darren_Steele)\ **Post date:** [February 18, 2025, 2:29pm UTC](https://forum.inductiveautomation.com/t/docker-volume-mount-point/102490/1 "2025-02-18T14:29:53Z")
Hi all, We host some docker containers that we let customers play with to test our product. For the longest time we've had issues whenever we take a container down and bring it up again because we had the ignition volume mapped to: volumes: - ignition-data:/usr/local/bin/ignition/data We had issues because we stored stuff in user-lib which is in the directory above data. So whenever we did a "docker compose down" we'd lose a bunch of stuff. I just did a quick test of mounting our volume at: volumes: - ignition-data:/usr/local/bin/ignition and all seems to work. I can take them down and bring them up and everything seems cool. Now, this goes against the general recommendations that I've read about on these forums so I'm just wondering about the implications of me changing the mount point as described above. Can anyone point out any flaws in my cunning plan? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 18, 2025, 2:56pm UTC](https://forum.inductiveautomation.com/t/docker-volume-mount-point/102490/2 "2025-02-18T14:56:12Z")
Not sure, but have you considered just making another volume and mount point for `user-lib` ? ---
**Author:** ![Darren\_Steele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/darren_steele/32/55624_2.png) [@Darren\_Steele](https://forum.inductiveautomation.com/u/Darren_Steele)\ **Post date:** [February 18, 2025, 2:59pm UTC](https://forum.inductiveautomation.com/t/docker-volume-mount-point/102490/3 "2025-02-18T14:59:39Z")
That did cross my mind, and that may well be a more elegant and safer solution. I'll give it a whirl ---
**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")
> [@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). ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 20, 2025, 12:17am UTC](https://forum.inductiveautomation.com/t/docker-volume-mount-point/102490/5 "2025-02-20T00:17:59Z")
Ha, I'm glad you saw this and responded. I had started responding to this yesterday to warn it would be trouble for upgrades, got distracted by something, and forgot about it entirely ---
**Author:** ![Darren\_Steele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/darren_steele/32/55624_2.png) [@Darren\_Steele](https://forum.inductiveautomation.com/u/Darren_Steele)\ **Post date:** [February 26, 2025, 8:08am UTC](https://forum.inductiveautomation.com/t/docker-volume-mount-point/102490/6 "2025-02-26T08:08:02Z")
Thanks for the input everyone. I've now implemented the bind point to site-packages and all seems to be working well and very pleased with the improvement. I do have a question about licenses but I'll start a fresh thread. Thanks again!