# BDOT Collector Container Images

The Bindplane Distro for OpenTelemetry (BDOT) Collector can be pulled from several container registries and offers multiple formats suitable for a variety of requirements.

### Registries

The BDOT Collector container images can be pulled from the following registries:

| Registry                                | Image                              | Architecture Support |
| --------------------------------------- | ---------------------------------- | -------------------- |
| **GitHub Container Registry** (default) | `ghcr.io/observiq/bindplane-agent` | `amd64`, `arm64`     |
| Docker Hub                              | `observiq/bindplane-agent`         | `amd64`, `arm64`     |

### Image Tags

There are two image tags available for each version:

#### Standard Image

* Format: `{{major.minor.patch}}`
* Example: `1.76.3`
* Base: Ubuntu

The standard image is used by default and supports all collector receivers as it contains the required\
Systemd libraries (Journald receiver) and Java runtime (JMX receiver).

#### Minimal Image

* Format: `{{major.minor.patch}}-minimal`
* Example: `1.76.3-minimal`
* Base: Scratch

The minimal image is a scratch-based container, suitable for environments requiring low surface area\
images. It does not contain the required dependencies to support `journald` or `JMX` receivers. It\
does support all Kubernetes sources, except the container logs source's `journald` input.


---

# Agent Instructions: 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:

```
GET https://docs.bindplane.com/deployment/docker/collector/bdot-collector-container-images.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.