Bitnami based Container Images don\u2019t have the application default paths within them, particularly for persistent data locations.<\/p>\n\n\n\n
An example is the Bitnami Postgres container images, which put the \/var\/lib\/postgres\/data directory in their own \/bitnami\/postgresql\/ directory.<\/p>\n\n\n\n
So if you configure your YAML or other deployment files for the application\u2019s default or long-standing expected directory paths, your containers may not persist your data as you\u2019d expect.<\/p>\n\n\n\n
It\u2019s worth checking Bitnami\u2019s own suggested YML files from\u00a0https:\/\/raw.githubusercontent.com\/bitnami\/containers\/main\/bitnami\/$APP\/docker-compose.yml<\/a>\u00a0where $APP is your container or application name.<\/p>\n\n\n\n See GitHub – bitnami\/containers: Bitnami container images \u00b7 GitHub<\/a> for more information and details.<\/p>\n","protected":false},"excerpt":{"rendered":" Bitnami based Container Images don\u2019t have the application default paths within them, particularly for persistent data locations. An example is the Bitnami Postgres container images, which put the \/var\/lib\/postgres\/data directory in their own \/bitnami\/postgresql\/ directory. So if you configure your … Continue reading