Merge pull request #224068 from tejaswikolli-web/gitissue#73733

added docker build arguments for git hub issue 73733

Author: prmerger-automator[bot]

articles/container-registry/container-registry-tasks-reference-yaml.md

@@ -136,8 +136,17 @@ steps:
     [property]: [value]
 ```
 
+Run the [az acr run][az-acr-run]command to get the docker version.
+
+```azurecli
+az acr run -r $ACR_NAME --cmd "docker version" /dev/null
+```
+
+Add environment variable `DOCKER_BUILDKIT=1` in yaml file to enable `buildkit` and use `secret` with `buildkit`.
+
 The `build` step type supports the parameters in the following table. The `build` step type also supports all build options of the [docker build](https://docs.docker.com/engine/reference/commandline/build/) command, such as `--build-arg` to set build-time variables.
 
+
 | Parameter | Description | Optional |
 | --------- | ----------- | :-------: |
 | `-t` &#124; `--image` | Defines the fully qualified `image:tag` of the built image.<br /><br />As images may be used for inner task validations, such as functional tests, not all images require `push` to a registry. However, to instance an image within a Task execution, the image does need a name to reference.<br /><br />Unlike `az acr build`, running ACR Tasks doesn't provide default push behavior. With ACR Tasks, the default scenario assumes the ability to build, validate, then push an image. See [push](#push) for how to optionally push built images. | Yes |

articles/container-registry/container-registry-tasks-scheduled.md

@@ -94,6 +94,7 @@ az acr task show --name timertask --registry $ACR_NAME --output table
 ```
 
 Run the [az acr task run][az-acr-task-run ] command to trigger the task manually.
+
 ```azurecli
 az acr task run --name timertask --registry $ACR_NAME
 ```