# Volume mount(s) for Docker container

**URL:** <https://forum.alta.inc/t/volume-mount-s-for-docker-container/4924>\
**Category:** Alta Control\
**Created:** [March 24, 2025, 3:53pm UTC](https://forum.alta.inc/t/volume-mount-s-for-docker-container/4924 "2025-03-24T15:53:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![chaz6](https://forum.alta.inc/user_avatar/forum.alta.inc/chaz6/32/3821_2.png) [@chaz6](https://forum.alta.inc/u/chaz6)\
**Post date:** [March 24, 2025, 3:53pm UTC](https://forum.alta.inc/t/volume-mount-s-for-docker-container/4924/1 "2025-03-24T15:53:03Z")

</div>

Could you please detail what directory/directories I need to mount for dynamic configuration/log directories? I would like to use volume mounts in order to persist the data on a specific storage driver (as well as persist the data when the container is rebuilt with Docker compose).

---

<div class="post-metadata">

**Author:** ![Alta-Josh](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-josh/32/2466_2.png) [@Alta-Josh](https://forum.alta.inc/u/Alta-Josh)\
**Post date:** [March 24, 2025, 4:33pm UTC](https://forum.alta.inc/t/volume-mount-s-for-docker-container/4924/2 "2025-03-24T16:33:59Z")

</div>

I created a compose file to help make better sense of the containers.

> [@On-premis container controller made easier](https://forum.alta.inc/t/on-premis-container-controller-made-easier/4193/14):
>
> I’ve developed a compose.yml for the current container. For those familiar with docker compose, this may help you out. services: control: image: altalabs/control:1.0d-amd64 container\_name: control-macvlan networks: control\_macvlan: # Customize for your network ipv4\_address: 10.166.0.10 tmpfs: - /run - /run/lock volumes: - /sys/fs/cgroup/access.scope:/sys/fs/cgroup:rw extra\_hosts: - local.manage.alta.inc:0.0.0.255 cgroup…

---

<div class="post-metadata">

**Author:** ![chaz6](https://forum.alta.inc/user_avatar/forum.alta.inc/chaz6/32/3821_2.png) [@chaz6](https://forum.alta.inc/u/chaz6)\
**Post date:** [March 24, 2025, 4:42pm UTC](https://forum.alta.inc/t/volume-mount-s-for-docker-container/4924/3 "2025-03-24T16:42:18Z")

</div>

Thanks, but that does not appear to contain any volumes for configuration. If I were to run `docker compose down && docker compose up` then all state would be lost.  
Edit: having had a poke of the docker container, it might be sufficient to mount `/var/lib/postgresql` in order to maintain state. Does that sound about right?

---

<div class="post-metadata">

**Author:** ![Alta-Josh](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-josh/32/2466_2.png) [@Alta-Josh](https://forum.alta.inc/u/Alta-Josh)\
**Post date:** [March 24, 2025, 4:48pm UTC](https://forum.alta.inc/t/volume-mount-s-for-docker-container/4924/4 "2025-03-24T16:48:20Z")

</div>

I haven’t had time to confirm all of the potential persistent data locations.

---

<div class="post-metadata">

**Author:** ![chaz6](https://forum.alta.inc/user_avatar/forum.alta.inc/chaz6/32/3821_2.png) [@chaz6](https://forum.alta.inc/u/chaz6)\
**Post date:** [March 24, 2025, 4:52pm UTC](https://forum.alta.inc/t/volume-mount-s-for-docker-container/4924/5 "2025-03-24T16:52:28Z")

</div>

Unfortunately it looks like the initial database files are part of the docker image, which means it’s not possible to mount it externally (unless you extract the initial files to your local volume first). Please consider looking at initializing the database within the container so that it is possible to persist the files to a Docker volume (e.g. on a dedicated storage array). It is difficult to manage Docker containers that do not provide volume mount locations for data that needs to be persisted. Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://forum.alta.inc/uploads/default/original/1X/087669c3d7c0a6495087b41d6f385a6771f2231c.png) [@system](https://forum.alta.inc/u/system)\
**Post date:** [June 11, 2026, 6:25am UTC](https://forum.alta.inc/t/volume-mount-s-for-docker-container/4924/6 "2026-06-11T06:25:45Z")

</div>


