# Docker installation using bind volume

**URL:** <https://forum.inductiveautomation.com/t/docker-installation-using-bind-volume/108781>\
**Category:** Ignition\
**Tags:** edge, docker\
**Created:** [July 22, 2025, 5:14pm UTC](https://forum.inductiveautomation.com/t/docker-installation-using-bind-volume/108781 "2025-07-22T17:14:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [July 22, 2025, 11:06pm UTC](https://forum.inductiveautomation.com/t/docker-installation-using-bind-volume/108781/2 "2025-07-22T23:06:37Z")

</div>

Sounds like you're worried about disk space based on your post in [this thread](https://forum.inductiveautomation.com/t/88585). Using a named volume versus a bind mount won't really change much for you here since you're referring to the storage layers of the container, not the volume. I'll let the other disk-space related discussion continue over in that other thread.

---

_[View the full topic](https://forum.inductiveautomation.com/t/docker-installation-using-bind-volume/108781)._