projections.milestones how to fix i cant find the solution
2025-07-07 14:31:03.827 UTC [76] ERROR: relation "projections.milestones" does not exist at character 63
2025-07-07 14:31:03.827 UTC [76] STATEMENT: SELECT instance_id, type, reached_date, last_pushed_date
FROM projections.milestones
WHERE reached_date IS NOT NULL
ORDER BY instance_id, reached_date;
7 Replies
its just copy to https://zitadel.com/docs/self-hosting/deploy/compose this link nothing added nothing increased just this
ZITADEL Docs
The setup is tested against Docker version 20.10.17 and Docker Compose version v2.2.3
Hey there @YokDaha I am happy to help but can I get a bit more details on what you're trying to do so I can better assist. Thanks in advance!
sorry
The setup process consistently fails when it attempts to create the projections.milestones table. Based on the zitadel-init container logs, all previous setup steps and migrations seem to execute correctly, but the process halts and exits with an error at this exact point.
This occurs on a clean installation after running docker compose down -v to ensure no data from previous attempts exists.
Environment Details:
Zitadel Image: ghcr.io/zitadel/zitadel:latest
Postgres Image: postgres:16-alpine
Configuration: All credentials and settings are confirmed to be consistent via a central .env file for all services. The database admin user has sufficient privileges to create the database and other tables.
Hypothesis:
This appears to be a specific incompatibility between the SQL command used to create projections.milestones in the setup script and the postgres:16 engine.
Core Question:
Is this a known issue? Is the setup migration script for projections.milestones fully compatible with Postgres 16, or should we be using a different version of Postgres (e.g., Postgres 15) for the current version of Zitadel? @Jim Morrison
Thank you for sharing the additional information here @YokDaha, I'll share this with the team and see what we can find.
ty bro
hello 👋 @YokDaha thanks for reaching out to us, can you try running
docker compose pull?🎉 Looks like you just helped out another community member! Thanks for being so helpful <@854908558415495188>! You're now one step closer to leveling up—keep up the amazing peer support! 🚀