-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AZD UP - deployment fails with indexer - logging into container registry #161
Comments
Same issue here. |
@dfberry I'm not sure what's causing the issue, but changing the region seems to fix it. We already experienced this and reported it in a different issue, I'll try to dig it up. |
Other possible fix for this issue, see #168 |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed. |
@dfberry is this still an issue, or can we close this one? |
I'm experiencing the same issue today with indexer failing to deploy. Followed the same steps as mentioned in the instruction, Here are the logs:
|
FYI @sinedied I just tried again with EAST US 2 region and a new resource group. Got the same error. TraceID this time: |
I am facing the same issue as @rockcs1992. I opened the issue #194 because i thought it was slightly different but I guess it's the same |
It seems that the latest infra update has caused an issue with the registry authentication. I'll have a look, thanks for the reporting. |
Fix is under review: #195 Should be merged quickly, thanks for your patience. |
Thanks @sinedied! |
The text was updated successfully, but these errors were encountered: