Library not found after upgrading to pro 6.3.7

Hi,

I have a seafile pro instance running with docker on my machine with AWS as object storage. I followed the upgrade instructions from the wiki (https://manual.seafile.com/deploy_pro/deploy_with_docker.html), and since the update, I cannot access my libraries anymore. Although they do display in the web interface, when I click on them the only error message is “library not found”. I tried to restore my latest backup, again following the instructions of the manual but to no avail.

There is nothing in the logs as far as I can see, all the files are still present in my AWS repo, the AWS credentials are still correct in seafile.conf, I have rebooted both the machine and the container multiple times and running docker exec -it seafile /bin/sh -c "seafile-server-latest/seaf-fsck.sh" returns the following:

Starting seaf-fsck, please wait ...

[11/12/18 22:50:43] fsck.c(602): Running fsck for repo 47a2882a-731b-4e22-a4d8-0920c75883e6.
[11/12/18 22:50:43] fsck.c(422): Checking file system integrity of repo My Library Template(47a2882a)...
[11/12/18 22:50:43] fsck.c(666): Fsck finished for repo 47a2882a.

[11/12/18 22:50:43] fsck.c(602): Running fsck for repo 2e405b9e-5527-469c-85d6-c8802af88f8e.
[11/12/18 22:50:43] repo-mgr.c(346): Commit 82cec1dca70ea19d167105fcbee5557f05fde126 is missing
[11/12/18 22:50:43] fsck.c(619): Repo 2e405b9e HEAD commit is damaged, need to restore to an old version.
[11/12/18 22:50:43] fsck.c(507): Scanning available commits...
[11/12/18 22:50:43] fsck.c(514): No available commits for repo 2e405b9e, can't be repaired.
[11/12/18 22:50:43] fsck.c(666): Fsck finished for repo 2e405b9e.

[11/12/18 22:50:43] fsck.c(602): Running fsck for repo 09981795-4c06-40bb-a41f-2e9bece71841.
[11/12/18 22:50:43] repo-mgr.c(346): Commit 80a5705d06abe18955187badd0f84f343b31243b is missing
[11/12/18 22:50:43] fsck.c(619): Repo 09981795 HEAD commit is damaged, need to restore to an old version.
[11/12/18 22:50:43] fsck.c(507): Scanning available commits...
[11/12/18 22:50:43] fsck.c(514): No available commits for repo 09981795, can't be repaired.
[11/12/18 22:50:43] fsck.c(666): Fsck finished for repo 09981795.

seaf-fsck run done

Hence my question, how the hell do I get my libraries to work again?

Most likely wrong file permissions. The container must be able to access and write the data.

I double checked, and the container does have permission to read/write to /seafile-data. Would something have changed between seafile pro 6.3.4 and 6.3.7 regarding AWS access?