WhMonkeyOriginal post
Rank 3: Container
Hello!
I've encountered a strange issue (but it also kinda makes sense). In the past, to turn off my Appwrite instance, I ran sudo docker compose down -v and when I started it again with sudo docker compose up -d, everything worked fine.
However, now when I run down -v and I start it again, all of my data is lost. It makes sense though as the down command also seems to take down the volumes, but why do this if the data is stored in the volumes.
Summary
Issue: When shutting down the container with 'sudo docker compose down -v' and starting it again, data is lost.
Solution: When shutting down the container, avoid using the '-v' flag to prevent volume deletion and data loss. Instead, use 'sudo docker compose down' to keep the data intact.