Error `No metadata for "X" was found` with custom entities after n8n-custom Dockerfile changes

[sebto]

• n8n version: 1.39.0
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system: Ubuntu 22

Hello everyone,

I’ve been running into an issue with custom entities after incorporating the recent changes to the n8n-custom Dockerfile (commit: refactor(core): Rebuild docker infrastructure (#8451) · n8n-io/n8n@1db35c1 · GitHub).

Our setup:

• Using n8n for the past 3 years
• Added three custom tables to the database (PostgreSQL) using migrations
• Added corresponding entities and repositories in the packages/cli/databases folder
• Everything worked fine until the mentioned Dockerfile changes

Now, we’re encountering the following error:

No metadata for "EventTriggerEventEntity" was found.

I’ve logged the following variables before instantiating our custom entity:

const con = Container.get(Connection);
console.log(con.entityMetadatasMap);
console.log(con.getMetadata('EventTriggerEventEntity')); 

Both logs show our custom entity metadata as expected. We can also instantiate n8n core entities like WorkflowEntity without any issues.

Has anyone else faced a similar problem after the Dockerfile changes? Or does anyone have a solution for this issue with custom entities?

Any help or guidance would be greatly appreciated!

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Jon]

Hey @sebto,

It seems unlikely that the error would be caused by the docker file change as that doesn’t change the database. I suspect a database migration we did has been missed and that has caused your database changes to do something odd.

Have you already been through the migrations and tried with a clean install without your database changes to see if that changes anything?