# Docker Volumes for Persistent Gateway Data

**URL:** <https://forum.inductiveautomation.com/t/docker-volumes-for-persistent-gateway-data/39378>\
**Category:** General Discussion\
**Tags:** ignition80\
**Created:** [October 5, 2020, 3:21pm UTC](https://forum.inductiveautomation.com/t/docker-volumes-for-persistent-gateway-data/39378 "2020-10-05T15:21:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 5, 2020, 3:31pm UTC](https://forum.inductiveautomation.com/t/docker-volumes-for-persistent-gateway-data/39378/2 "2020-10-05T15:31:29Z")

</div>

Not quite - on the official images, the entire service is installed to `/usr/local/bin/ignition`, rather than the ‘exploded’ path we used in previous versions - so the equivalent path would be `/usr/local/bin/ignition/data`. Not that Ignition as a whole has some limitations with single volume persistence like this; backing up the `/data` directory will capture the internal database and projects, which is 90% of what you would want to restore, but it does omit any custom JDBC driver files, modules or Python libraries you’ve installed (all of which are in `${install dir}/user-lib/`).

---

_[View the full topic](https://forum.inductiveautomation.com/t/docker-volumes-for-persistent-gateway-data/39378)._