> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/deployment/docker/collector/bdot-collector-architecture.md).

# BDOT Collector Architecture

Deploy Bindplane Collectors with Docker Compose

Deploying a Bindplane Distribution for OpenTelemetry (BDOT) Collector with Docker Compose is based on the Linux installation.

#### Docker Compose Service

The BDOT Collector is deployed as a service in a Docker Compose network.

**Supported Integrations**

Just as with the Linux, Mac, and Windows installation, all integrations are supported.

* [Sources](/integrations/sources.md)
* [Destinations](/integrations/destinations.md)
* [Processors](/integrations/processors.md)

{% hint style="info" %}
**NOTE**

Please note certain sources require special setup to work correctly, and may not always behave as expected. If you encounter any strange behavior, please let us know in our [Slack Community](https://www.launchpass.com/bindplane/free)!
{% endhint %}

**Configuration**

The BDOT Collector makes use of `storage` and `config` directories when mounted.

```
> config
    manager.yaml
> storage
    config.yaml
    logging.yaml
  docker-compose.yaml
```

Volume mounts:

```yaml
volumes:
    - ./config:/etc/otel/config
    - ./storage:/etc/otel/storage
```

### Limitations

#### Collector Version Upgrade

Container-based collectors are bound to the version which is specified in Docker. To change to a new version, you can re-deploy the collectors by editing the version in Docker Compose, and redeploying the collector.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bindplane.com/deployment/docker/collector/bdot-collector-architecture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.