ClementineC
ZITADELβ€’4mo agoβ€’
10 replies
Clementine

Persistent zitadel-init failure

Hello everyone,
I'm running into a persistent issue with my Zitadel Docker Compose setup and I'm hoping someone can spot what I'm missing.

The Situation:
I'm trying to deploy Zitadel and can successfully reach the UI on my domain. However, looking at the logs for my PostgreSQL container (db-1), I can see the initialization is failing and both zitadel-init and zitadel seems running .
I set up a docker-compose.yaml with de db postgres container, a zitadel-init container and a zitadel set-up container. I also configure nginx (TLS mode external).

Here the logs :
db-1 | 2025-09-23 17:45:28.429 UTC [1] LOG: database system is ready to accept connections
db-1 | 2025-09-23 17:45:32.852 UTC [56] ERROR: database "zitadel" already exists
db-1 | 2025-09-23 17:45:32.852 UTC [56] STATEMENT: CREATE DATABASE "zitadel"
zitadel-init-1 | time="2025-09-23T17:45:55Z" level=info msg="server is listening on [::]:8080" caller="/home/runner/work/zitadel/zitadel/cmd/start/start.go:508"
zitadel-1 | time="2025-09-23T17:45:54Z" level=info msg="server is listening on [::]:8080" caller="/home/runner/work/zitadel/zitadel/cmd/start/start.go:508"

My Question:
Could someone help me understand how to configurate my zitadel and what am I missing ?
Was this page helpful?