Error deploying Aspire app, failure to deploy dashboard

Question

I'm getting an error trying to deploy an Azure container app from aspire using 'azd provision'

I've configured the bicep so that the container apps environment is 'consumption only' and inside a vnet.

The error I get on provision or if I manually try and enable the aspire dashboard is:

"Failed to provision component 'aspire-dashboard'. Error details: Failed to create config map external-auth-config-map for DotNetComponent aspire-dashboard in k8se-telemetry namespace. There will be no re-tries.."

I'm not sure why this isn't working. I have other consumption only container app environments with aspire deployed, so I guess it's not happy with the vnet attachment, but no clue why or how to proceed.

Answer 1

Hello Matthew Paul,

The error message indicates a failure to create a config map, which could be due to network restrictions or permissions issues within the VNet.

• First ensure that the VNet is properly configured to allow communication between the Azure Container Apps and any necessary Azure services. Review the network security groups and routing to confirm that there are no restrictions blocking the required traffic.
• Make sure that the necessary permissions are assigned to your Azure account for managing resources within the VNet. You may need to explicitly assign yourself the Contributor or Owner role on the Container Apps environment.
• Also, check the logs for more detailed error messages. This can provide additional context on what might be failing during the provisioning process.

Note: If possible, try deploying the Aspire dashboard in a non-VNet environment to see if the issue persists. This can help isolate whether the VNet configuration is the root cause.

Also, refer the mention documents to troubleshoot the issue better and for better understanding and from the GitHub as well as from Microsoft refer the below documents.

• Deploy a .NET Aspire project to Azure Container Apps
• Dashboard configuration

If you have any further concerns or queries, please feel to reach out to us and if possible, please try to share the error screenshots if any.