Upgrade to 8.0.10/11 Fails

I’ve been using Seafile for quite some time (probably 1-1.5 years), haven’t had an issue at all until now.
Upgraded from (I believe) 8.0.9 to 8.0.10, and got this error:

[09/27/2021 00:14:13][upgrade]: Running script /opt/seafile/seafile-pro-server-8.0.11/upgrade/minor-upgrade.sh

This script would do the minor upgrade for you.
Press [ENTER] to contiune

renaming the gunicorn.conf to gunicorn.conf.py …

Failed to renamed the gunicorn.conf to gunicorn.conf.py.
[2021-09-27 00:14:13] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.
Traceback (most recent call last):
File “/scripts/start.py”, line 86, in
File “/scripts/start.py”, line 58, in main
File “/scripts/upgrade.py”, line 172, in check_upgrade
File “/scripts/upgrade.py”, line 84, in run_minor_upgrade
run_script_and_update_version_stamp(minor_upgrade_script, current_version)
File “/scripts/upgrade.py”, line 61, in run_script_and_update_version_stamp
File “/scripts/utils.py”, line 70, in call
return subprocess.check_call(*a, **kw)
File “/usr/lib/python3.8/subprocess.py”, line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘/opt/seafile/seafile-pro-server-8.0.10/upgrade/minor-upgrade.sh’ returned non-zero exit status 1.

Same issue happens with 8.0.11 (different upgrade script listed as failing, 8.0.11 listed instead of 8.0.10).

Ubuntu Linux
Seafile pro in a docker container, started via docker-compose

When I try to docker pull anything prior to 8.0.10 (8.0.[0-9]), I get:
docker pull (truncaterd due to posting link limitation)/seafileltd/seafile-pro-mc:8.0.9
Error response from daemon: manifest for (truncaterd due to posting link limitation)/seafileltd/seafile-pro-mc:8.0.9 not found: manifest unknown: manifest unknown

I’ve always used the latest tag. Not sure how to:

  1. Get seafile running again, since the version I probably used doesn’t seem to be in the registry anymore
  2. How can I go about fixing the script migration error?

Thanks for any information that you can provide

Nevermind, issue was entirely on my side. After a reboot, drive mappings didn’t go back to the way they were supposed to, so it was missing data.
After that was fixed, issues resolved.