Azure-Samples / Azure-Samples/dotNET-FrontEnd-to-BackEnd-on-Azure-Container-Apps
Build Step - Login To ACR Failed
- Dominant language
- Bicep
- Stars
- 76
- Forks
- 248
- PR merge metrics
- No merged PRs in 30d
Description
> Please provide us with the following information:
> ---------------------------------------------------------------
### This issue is for a: (mark with an `x`)
```
- [ 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
> Run deploy.yml All steps before this step succeeded.
### Any log messages given by the failure
>
### Expected/desired behavior
>
### OS and Version?
> Windows 10
[LoginToACR-Failed.zip](https://github.com/Azure-Samples/dotNET-FrontEnd-to-BackEnd-on-Azure-Container-Apps/files/9162022/LoginToACR-Failed.zip)
### Versions
>
### Mention any other details that might be useful
> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.
Contributor guide
Research direction
Start by reading deploy.yml and reviewing the attached LoginToACR-Failed.zip for the failing build-step output. Reproduce the deployment on Windows 10 and determine why the ACR login fails; done means the deploy workflow completes that step successfully with the failure understood and covered by the available evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- ci-cd, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100