Answer the question
In order to leave comments, you need to log in
What is the preferred Postgres containerization strategy?
Suppose there is some multi-module docker application. Which uses postgres as a database. Postgres is also running in a container. But the question arises, if you need to update the container with Postgres, then all the data that was saved in the database will be lost. Correctly?
What is the best way to organize the launch of Postgres in a container in this case?
Only one idea is spinning in my head, to mount an external drive to the path where postgres saves the database file structure, and after updating the image, the data folder will already be available with all the old data.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question