Closed ezYakaEagle442 closed 1 year ago
is it because the container name in the UPPERCASE ?
What about https://github.com/Azure/cli/blob/master/src/main.ts#L73 where the volume settings -v is set without quotes "" whereas it should be wrapped by "" as suggested at https://stackoverflow.com/questions/48522615/docker-error-invalid-reference-format-repository-name-must-be-lowercase
This issue is stale because it has been open for 7 days with no activity.
This issue is idle because it has been open for 14 days with no activity.
Hi @ezYakaEagle442
The container name is not the issue as we can have any name for the container. I also don't think volume should cause such issues as the possibility of them having a space seems negligible unless in some custom environment where env variables are set incorrectly.
To be double sure about the volume, I have a created a new build with double quotes around the volume which can be accessed by changing the @v1
to @t-dedah/test-volumne-with-double-quotes
. The updated block
- name: Azure CLI script
uses: azure/CLI@t-dedah/test-volumne-with-double-quotes
with:
azcliversion: 2.40.0
inlineScript: |
az account show
az storage -h
Meanwhile we will try to replicate the issue.
This issue is stale because it has been open for 7 days with no activity.
This issue is idle because it has been open for 14 days with no activity.
Closing this issue for now. Please reopen if you have more followup questions.
running azure/CLI fails with "invalid reference format: repository name must be lowercase"
https://github.com/ezYakaEagle442/aca-java-petclinic-mic-srv/blob/main/.github/workflows/deploy-iac.yml#L77
see https://github.com/ezYakaEagle442/aca-java-petclinic-mic-srv/actions/runs/3141520108/jobs/5104050174