Migrating from old (blacklisted!) unRaid docker container

I installed Sf on my unRaid a long time ago and it’s been working great with SeaDrive on my Win11 laptop. I recently had to replace that laptop and thought I’d install the Sf client to my Android phone as well.

That’s when I realized the problem.

The web ui says I’m running Server Version: 6.3.4. My unRaid server doesn’t provide an automated way of upgrading it and checking the info under “installed apps” tells me this:

Blacklisted: Unable to be pulled
This application template has been blacklisted.

The unRaid community apps offer Sf 10-13.

How do I safely upgrade and migrate my files?

Again: I don’t have any local copies since the laptop is gone and I can’t download from the web ui for some reason.

Here is a possible way to solve the issue (suggested by AI):


Directly jumping from Seafile 6.3.4 to modern versions (10–13) is not supported. Seafile requires running sequential database upgrade scripts across each major version (6.3 → 7.0 → 7.1 → 8.0, etc.), and attempting a multi-version leap by mounting legacy data directly into a modern container will likely corrupt the database or fail to start.

Because your primary goal is to safely recover your files without a working client or web download, the recommended and safest route is to export your data directly from the storage backend rather than attempting a multi-step upgrade chain across obsolete containers.

Step 1: Back up existing appdata

Before running any commands, make a complete backup copy of your current Seafile appdata directory (including database files, configuration, and the seafile-data folder) on unRaid.

Step 2: Export files using seaf-fsck

Seafile includes a built-in tool called seaf-fsck that can reconstruct and export all files from unencrypted libraries directly to the file system without needing the web UI or database.

  1. Open a terminal or console into your running Seafile container:
    docker exec -it <seafile-container-name> bash
    
  2. Run the export command:
    cd /opt/seafile/seafile-server-latest
    ./seaf-fsck.sh --export /path/to/export_dir
    
    Make sure /path/to/export_dir maps to a host path or unRaid share with sufficient free storage space.

Note that seaf-fsck --export only works on unencrypted libraries. If you have encrypted libraries, you would need to use seaf-fuse to mount them read-only.

For more details on using seaf-fsck, refer to the official documentation:

Step 3: Deploy a fresh modern Seafile instance

Once you have exported and verified your files on unRaid storage:

  1. Stop and remove the obsolete container.
  2. Install a current, supported Seafile container template from the unRaid Community Applications.
  3. Configure your users and libraries freshly, then upload or sync your recovered files back into the new setup.