> 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/kubernetes/collector/images.md).

# Images

The Bindplane Collector can be pulled from several container registries and offers multiple formats\
suitable for a variety of requirements.

### Registries

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

<table><thead><tr><th>Registry</th><th width="380.48046875">Image</th><th>Architecture Support</th></tr></thead><tbody><tr><td><strong>GitHub Container Registry</strong> (default)</td><td><code>ghcr.io/observiq/bindplane-agent</code></td><td><code>amd64</code>, <code>arm64</code></td></tr><tr><td>Docker Hub</td><td><code>observiq/bindplane-agent</code></td><td><code>amd64</code>, <code>arm64</code></td></tr><tr><td>Google Artifact Registry</td><td><code>us-central1-docker.pkg.dev/observiq-containers/agent/bindplane-agent</code></td><td><code>amd64</code>, <code>arm64</code></td></tr></tbody></table>

### Image Tags

There are two image tags available for each version:

#### Standard Image

* Format: `{{major.minor.patch}}`
* Example: `1.55.0`
* 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.55.0-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
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/kubernetes/collector/images.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.