Azure-Samples / Azure-Samples/java-on-aca
Error During create Container apps
- Langage dominant
- CSS
- Étoiles
- 15
- Forks
- 247
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
It looks like the error you're encountering is due to the Azure Container Registry (ACR) resource not being found in my specified subscription.
I am getting Error after running this command
az containerapp create \
--name $APP_NAME \
--resource-group $RESOURCE_GROUP \
--ingress external \
--target-port 8080 \
--environment $ACA_ENVIRONMENT \
--min-replicas 1 \
--artifact ./spring-petclinic-api-gateway/target/spring-petclinic-api-gateway-$VERSION.jar \
--bind $JAVA_CONFIG_COMP_NAME $JAVA_EUREKA_COMP_NAME \
--runtime java
Error Message
Role assignment failed with error message: "The resource with name 'XXXXXX' and type 'Microsoft.ContainerRegistry/registries' could not be found in subscription 'XXXXXXXXXXX'.".
To add the role assignment manually, please run 'az role assignment create --assignee XXXXXXXX --scope --role acrpull'.
You may have to restart the containerapp with 'az containerapp revision restart'.
- Running ..Failed to provision revision for container app 'api-gateway'. Error details: Operation expired.
> Please provide us with the following information:
> ---------------------------------------------------------------
### This issue is for a: (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```
### Minimal steps to reproduce
>
### Any log messages given by the failure
>
### Expected/desired behavior
>
### OS and Version?
> Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
### Versions
>
### Mention any other details that might be useful
> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par la commande az containerapp create et les messages ACR signalés role-assignment et revision-expired. Reproduisez l’échec avec l’artefact et les ressources Azure indiqués, puis confirmez que la commande provisionne api-gateway avec succès ou documentez la portée de registre requise et les étapes de redémarrage.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- azure, java, spring
- Domaine
- cloud, devops
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100