> For the complete documentation index, see [llms.txt](https://docs.meterian.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meterian.io/ci-server-integrations/azure-devops/using-the-docker-image.md).

# Using the Docker image

If you decide to use the Docker Image with your Azure pipeline, you will need to update the configuration file **azure-pipelines.yml** with this small snippet, which will invoke the client:

```
- script: |
    docker run --rm \
    --volume ${PWD}:/workspace --env METERIAN_API_TOKEN=$(METERIAN_API_TOKEN) \
    meterian/cli [Meterian CLI Options]
  displayName: 'Run Meterian'
```

The only requirement is for the base image to have docker installed (most images do, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops) for details). A working example of the non-native integration via Docker can be found [here](https://dev.azure.com/meterianrocksolid/_git/java-sample-project-non-native?path=%2Fazure-pipelines.yml). 

Meterian will be launched against the project source code every time a new change is committed and pushed in your repository. Rember to set the METERIAN\_API\_TOKEN environment variable, see the [Azure Devops](/ci-server-integrations/azure-devops.md) section for instructions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.meterian.io/ci-server-integrations/azure-devops/using-the-docker-image.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.