fails to persist data across container removal and restart about paradedb

[philippemnoel]

Hi @34code. Thank you for reporting this. This is an oversight on our end, in that we haven't yet published to Docker Hub the new image based on Bitnami. Once #938 is merged, this should no longer be an issue.

I'll keep this open for now, and we'll do a release today to fix your issue

[34code]

Thank you!

[34code]

fixed in v0.5.8.. only thing I would make clearer in docs is that the directory mapped in volumes: needs to be writable by a user with uid = 1001. I ran the following commands and everything is working smoothly from a persistence perspective!

sudo useradd -u 1001 compose
chown compose /fast/paradedb/postgresql_data

^^ so that docker compose can write to the path I specified. Seems like a bitnami requirement..

[philippemnoel]

#952 will close the doc issue. Thank you for reporting!

[philippemnoel]

fixed in v0.5.8.. only thing I would make clearer in docs is that the directory mapped in volumes: needs to be writable by a user with uid = 1001. I ran the following commands and everything is working smoothly from a persistence perspective!

sudo useradd -u 1001 compose chown compose /fast/paradedb/postgresql_data

^^ so that docker compose can write to the path I specified. Seems like a bitnami requirement..

Yeah it is a bitnami requirement. I'll re-open the issue and add clarification