Replies: 4 comments
-
Is there a bug to report here, or are you just posting it as a warning for others? |
Beta Was this translation helpful? Give feedback.
-
It's absolutely a defect here, please try it, your postgres database volume left be empty and you'd lose db data whenever you upgrade postgres image. |
Beta Was this translation helpful? Give feedback.
-
You can choose to pass environment variables to the postgres container however you want. Passing And yes, setting PGDATA to a location that you don't actually create a volume mount for sounds like a bad idea. Alternatively we can delete the |
Beta Was this translation helpful? Give feedback.
-
What is the purpose of In the document, the description for |
Beta Was this translation helpful? Give feedback.
-
The bug
DO NOT USE PGDATA as variable which will overwrite the internal one(postgres pre-defined) , lead the container to create the database you defined at $PGDATA and leave /var/lib/postgresql/data empty
this is why every time upgrade database cause breaking.
try use PG_DB_DATA
volumes:
- ${PG_DB_DATA}:/var/lib/postgresql/data
The OS that Immich Server is running on
Arch
Version of Immich Server
latest
Version of Immich Mobile App
latest
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions