Hey everyone! I've been trying to deploy my Container App environment using Bicep, and it's been running for about 1.5 hours without any progress showing in the Activity log. These environments are being set up inside a VNet. I noticed that some resource groups were created and then deleted during the process, and I'm wondering if this is normal. I suspect there might be an issue with my managed certificate setup, so I'm considering canceling the deployment for now. Last year, I encountered a bug that caused similar issues, so I'd love any suggestions you might have! By the way, I resolved my previous issues by modifying the workload profile and managing the certificate setup differently. Looking forward to your insights!
3 Answers
If the deployment is taking over 10 minutes without any logs, it could be a permissions issue. Make sure you have the right permissions set for accessing resources. Also, reviewing your Bicep code might help pinpoint what's wrong—sometimes it’s just a little fix needed!
It sounds like the deployment might be taking longer due to the complexities of the Azure environment. Sometimes, the services connected to your app, like Private Links, can cause delays if they're not properly approved or configured. Double-check your Azure Container Registry as well; if the image you need isn't there or isn't accessible, that could definitely hold things up too.
Honestly, I decided to steer clear of container apps after too many issues like this. Switching to VMs made my life a lot easier! You might want to consider that option if your project allows it.
I realized it's definitely something to do with my Bicep code after looking into it further. Thanks for the tip!