az acr build fails when using --build-arg, but works without it

[hamzaadevops]

Describe the bug

I am using az acr build in a GitHub Actions workflow to build and push a Docker image to Azure Container Registry (ACR).

The following command works fine:

az acr build --image ${{ env.AZURE_CONTAINER_REGISTRY }}.azurecr.io/${{ env.CONTAINER_NAME }}:${{ github.sha }} \
  --registry ${{ env.AZURE_CONTAINER_REGISTRY }} \
  -g ${{ env.ACR_RESOURCE_GROUP }} \
  -f ${{ env.DOCKER_FILE }} \
  ${{ env.BUILD_CONTEXT_PATH }}

Related command

But this command gives us the error as shown in the screenshot

az acr build --image ${{ env.AZURE_CONTAINER_REGISTRY }}.azurecr.io/${{ env.CONTAINER_NAME }}:${{ github.sha }} \
  --registry ${{ env.AZURE_CONTAINER_REGISTRY }} \
  -g ${{ env.ACR_RESOURCE_GROUP }} \
  -f ${{ env.DOCKER_FILE }} \
  --build-arg AZURE_COMMUNICATION_SERVICES_CONNECTION_STRING=${{ secrets.AZURE_COMMUNICATION_SERVICES_CONNECTION_STRING }} \
  --build-arg AZURE_COMMUNICATION_SENDER_EMAIL=${{ secrets.AZURE_COMMUNICATION_SENDER_EMAIL }} \
  --build-arg AZURE_COMMUNICATION_RECIPIENT_EMAIL=${{ secrets.AZURE_COMMUNICATION_RECIPIENT_EMAIL }} \
  ${{ env.BUILD_CONTEXT_PATH }}

Errors

However, when I add --build-arg options, the command fails with the error:
"the following arguments are required: <SOURCE_LOCATION>"

Expected behavior

Both versions of the command should work as expected. Adding --build-arg should not break the az acr build command.

Actual Behavior:
Adding --build-arg results in the following error:
ERROR: the following arguments are required: <SOURCE_LOCATION>

Additional context

I confirmed that the Dockerfile and build context exist
The same command works locally, but fails in GitHub Actions
Possible issue with how az acr build handles --build-arg in GitHub Actions?

[yonzhan]

Thank you for opening this issue, we will look into it.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• az acr build #19009
• --build-arg causes failed builds in Azure Container Registry #8305

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

In general this issue is because of quotes. We interpret the command as if it were written directly to a shell. So if there's a space, or a special character like &, then the shell interprets that and decides how to split args. In general though you can fix all of these by doing something like foo='bar qux &'

Reference:

• --build-arg causes failed builds in Azure Container Registry #8305 (comment)

Solution 2:

For now, I’d suggest you encode such value with multiple lines or spaces to single line base64 string (eg, base64 -w 0) and pass to —build-arg or —set. On your Dockerfile file or build script, decoded it to the original value.

Reference:

• --build-arg causes failed builds in Azure Container Registry #8305 (comment)

Powered by issue-sentinel

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @toddysm, @luisdlp, @northtyphoon, @terencet-dev.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @toddysm, @luisdlp, @northtyphoon, @terencet-dev.

[terencet-dev]

Looking into this and will triage/prioritize accordingly