Timeline for data lost while restarting postgres with docker
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2, 2016 at 4:32 | comment | added | kampta | I believe I don't know how to use persistent volumes properly. How do I specify a data directory for postgres, such that in case container is destroyed, I can start a new container with existing data directory? | |
| Oct 2, 2016 at 4:29 | comment | added | kampta |
My bad, I think I might have started a new container when I changed the name of directory containing docker-compose.yml. I thought specifying the container_name variable, will resolve the issue (i.e. up -d will start the same container as before all the time)
|
|
| Oct 1, 2016 at 20:43 | history | answered | RichArt | CC BY-SA 3.0 |