Build Step - Login To ACR Failed

[mggillen]

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

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

[hesperanca]

Same issue here. The error I'm getting at the LoginToACR step is:

parse error: Invalid numeric literal at line 1, column 8
Error: Process completed with exit code 4.

[joudot]

Not sure if it is the same as you all but I got an error in the following step Deploy Container Apps although the docker login command seems successful.

ERROR: Failed to retrieve credentials for container registry. Please provide the registry username and password

[mggillen]

Not sure if it is the same as you all but I got an error in the following step Deploy Container Apps although the docker login command seems successful.

ERROR: Failed to retrieve credentials for container registry. Please provide the registry username and password

Not actually even getting that far. The command just before the docker login is what is failing for me.
RE: refresh_token=$(curl https://${{ env.RESOURCE_GROUP_NAME }}acr.azurecr.io/oauth2/exchange -v -d "grant_type=access_token&service=${{ env.RESOURCE_GROUP_NAME }}acr.azurecr.io&access_token=$access_token" | jq -r .refresh_token

I believe the issue is related to the pipe "|jq -r .refresh_token" If I run that command above without the pipe to the "jq" command then I'll get the error you described.

[mggillen]

Same issue here. The error I'm getting at the LoginToACR step is:

parse error: Invalid numeric literal at line 1, column 8 Error: Process completed with exit code 4.

Yep, that's exactly the error I got.