In fact it's kind of normal as the volumes are created by the restore script, but the script requires this :
# Make sure the Appwrite did NOT run on this server previously,
# and make sure to stop it before this restore.
# If appwrite ran here already, make sure to
# stop Appwrite with 'docker-compose down -v', and ideally
# also remove appwrite folder.
Doing so I'm ending with a clean server on which the script is restoring, creating new volumes but losing the compose link. It's finally working well, but a docker volume inspect clearly shows that it's missing the "link". Here is from a docker-compose install :
[
{
"CreatedAt": "2023-02-26T18:16:04Z",
"Driver": "local",
"Labels": {
"com.docker.compose.project": "appwrite",
"com.docker.compose.version": "2.5.0",
"com.docker.compose.volume": "appwrite-certificates"
},
"Mountpoint": "/docker/var/lib/docker/volumes/appwrite_appwrite-certificates/_data",
"Name": "appwrite_appwrite-certificates",
"Options": null,
"Scope": "local"
}
]
and after a restore (note the missing "Labels" that maintain the docker-compose source) :
[
{
"CreatedAt": "2023-04-19T13:07:31Z",
"Driver": "local",
"Labels": null,
"Mountpoint": "/var/lib/docker/volumes/appwrite_appwrite-certificates/_data",
"Name": "appwrite_appwrite-certificates",
"Options": null,
"Scope": "local"
}
]
BTW, the above samples come from 2 different platforms but I got the same before/after changes on the same server.