dify deployed version 1.13.3, then migrated the data volumes from version 1.8.1 to version 1.13.3, and performed an upgrade operation. However, an issue arose with the non-existent datasource_installations table. Attempts to execute the docker compose exec api flask db upgrade command and revert to a previous version for re-execution were unsuccessful. Finally, an attempt to migrate the historical data volumes again and perform the upgrade operation still did not resolve the issue. How should this be handled

[DGdVPW]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

dify deployed version 1.13.3, then migrated the data volumes from version 1.8.1 to version 1.13.3, and performed an upgrade operation. However, an issue arose with the non-existent datasource_installations table. Attempts to execute the docker compose exec api flask db upgrade command and revert to a previous version for re-execution were unsuccessful. Finally, an attempt to migrate the historical data volumes again and perform the upgrade operation still did not resolve the issue. How should this be handled

2. Additional context or comments

No response

[DGdVPW]

docker compose exec db psql -U <database_username> -d -c "\l" ，exists database named dify_plugin,use this database to create table that can solve this problem

[dosubot[bot]]

Hi @DGdVPW! I'm Dosu and I'm helping the Dify team.

You're on the right track — the dify_plugin database is used by the Plugin Daemon service and needs its tables initialized separately from the main dify database [1]. However, rather than manually creating individual tables, you should run the Plugin Daemon's built-in migration command to create all required tables at once:

docker exec -it plugin_daemon /app/commandline migrate

This will create the expected tables in the dify_plugin database, including plugin_installations, tool_installations, ai_model_installations, and agent_strategy_installations [2] [3].

After running the migration, restart the containers:

docker compose down && docker compose up -d

Note: The table you're looking for might actually be plugin_installations rather than datasource_installations — there's no datasource_installations table in the standard Dify schema. If the migration command above resolves the error, that confirms it was just missing table initialization in the plugin database.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[omni-front]

it looks like the upgrade process missed creating the datasource_installations table, which might be due to a migration script not running properly. first, check if the table is supposed to exist by reviewing the migration files to see if one of them should create it. if so, you can manually apply that migration using the flask db stamp command to mark the current migrations as applied, or flask db migrate to regenerate one if missing. also, ensure that your database user has the right permissions to make schema changes, as this can sometimes block migrations from executing properly.