_thegoldenegg_
_thegoldenegg_13mo ago

Is there anyone who has successfully deployed zitadel to azure container apps?

I'm trying to deploy zitadel to azure container apps, postgres database is already deployed and it's working and it is reachable by the other apps in the same rg, however when i try to deploy zitadel it doesn't work at all it just stops, I tried using this in command override "start-from-init" and arguments override '--masterkey "masterkeyhere", --tlsMode disabled' but it still doesn't work, anyone here tried it before?
9 Replies
FFO
FFO13mo ago
Can you share logs you have?
_thegoldenegg_
_thegoldenegg_OP13mo ago
I get these two error logs: time="2024-10-21T13:38:21Z" level=panic msg="none of the enabled methods for identifying the machine succeeded" caller="/home/runner/work/zitadel/zitadel/internal/id/sonyflake.go:142" errors="failed to get Private IP address no private ip address, failed to query metadata webhook Get "http://metadata.google.internal/computeMetadata/v1/instance/id\": dial tcp: lookup metadata.google.internal on 127.0.0.11:53: no such host" then some info logs then : time="2024-10-21T13:38:36Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:130" migration step=03_default_instance it stays like that until it fails Btw, in azure i had to only use the "Override arguments" field just like this : "start-from-init, --masterkey, your32charkeyhere, --tlsmode, disabled" now I have these errors above.
FFO
FFO13mo ago
I see. Zitadel needs to have a unique name/ip for its id generator. You can configure this here https://github.com/zitadel/zitadel/blob/main/cmd/defaults.yaml#L217 In your case we might need to disable the google part and enable the hostname. Not sure thoug if each container has its unique name in Azure 😁
_thegoldenegg_
_thegoldenegg_OP13mo ago
Is there a way to access this config as environment variable? and what should be the value in there?
FFO
FFO13mo ago
Yeah sure thats the part ZITADEL_MACHINE_IDENTIFICATION_WEBHOOK_ENABLED which is the ENV
FFO
FFO13mo ago
Uhm could be, not sure about the url with azure Thing is the metadata might not have the same body 😅 So I think we should try IP/Hostname
_thegoldenegg_
_thegoldenegg_OP13mo ago
It seems it's the right url as stated in Microsoft QA, however it's unreachable, and could have a different body even if it was reachable. I did make it start by using the following env vars: ZITADEL_MACHINE_IDENTIFICATION_HOSTNAME_ENABLED set to true and ZITADEL_MACHINE_IDENTIFICATION_WEBHOOK_ENABLED to false, however i'm facing another issue now: unable to set instance using origin &{zitadel.xxxxxxxx.francecentral.azurecontainerapps.io https} (ExternalDomain is localhost): ID=QUERY-1kIjX Message=IAM not found.
FFO
FFO13mo ago
Yeah but this is just a matter of configuring the external domain name with ZITADEL_EXTERNALDOMAIN

Did you find this page helpful?