After update to 4.18.0 containers refuse to start
🏬Self-hosted🪲Bugs✅Solved
Just updated to 4.18.0, and Zitadel and the login container refuse to start.
It appears to be due to this change: https://github.com/zitadel/zitadel/pull/12740
Looks like no migration was run on container startup to add these relations, yet the application is looking for them.
I will send full error output momentarily.
It appears to be due to this change: https://github.com/zitadel/zitadel/pull/12740
Looks like no migration was run on container startup to add these relations, yet the application is looking for them.
I will send full error output momentarily.
GitHub
Which Problems Are Solved
Bulk unique-constraint deletes (org, IDP with many links, user, project) reconstruct every uniqueness key in Go and emit N DELETEs. That can OOM on large tenants.
A one-sh...
Bulk unique-constraint deletes (org, IDP with many links, user, project) reconstruct every uniqueness key in Go and emit N DELETEs. That can OOM on large tenants.
A one-sh...
