[NEOS-458] Investigate Database Docker Volume missing file and permission issues about neosync HOT 3 CLOSED

Some steps to try and reproduce this are:

1. Stand up neosync via Tilt
2. Shut down tilt
3. Stand up neosync via Docker Compose

I'm wondering if this is an issue with our Tilt DB using the bitnami/postgresql image instead of the official postgres image.

If so, we should look into migrating away from bitnami/postgresql for Tilt pg and instead use the official image.

from neosync.

A native solution would be to have Tilt and Compose use separate .datapersistence layers, but I'd like to share them just so you can seamlessly go between these environments and your postgres data stays the same.

from neosync.

This is no longer an issue as we've moved to using native docker volumes in place of mounting them to the host system for docker compose. Thus, compose and tilt no longer conflict or have issues.

from neosync.