-
- Notifications
You must be signed in to change notification settings - Fork 123
Closed
Labels
bugSomething isn't workingSomething isn't workingdockerPull requests that update Docker codePull requests that update Docker codepriority:high
Description
After upgrading GreedyBear to version 3.0.0 on one of my instances all historic data disappeared. After some investigation I noticed that the application uses the wrong docker volume.
> sudo docker inspect greedybear_postgres --format '{{json .Mounts}}' | python3 -m json.tool [ { "Type": "volume", "Name": "5ed93ca33747f82767cf26389827376700ca472dbeb05a5fff8ab9f759f87e07", "Source": "/var/lib/docker/volumes/5ed93ca33747f82767cf26389827376700ca472dbeb05a5fff8ab9f759f87e07/_data", "Destination": "/var/lib/postgresql", "Driver": "local", "Mode": "", "RW": true, "Propagation": "" }, { "Type": "volume", "Name": "greedybear_postgres_data", "Source": "/var/lib/docker/volumes/greedybear_postgres_data/_data", "Destination": "/var/lib/postgresql/data", "Driver": "local", "Mode": "z", "RW": true, "Propagation": "" } ] As can be seen, there are two volumes available for the postgres container. After the update, for some reason the application decided to use the first one, although the data lives in the second one.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingdockerPull requests that update Docker codePull requests that update Docker codepriority:high