> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/2.34.0/getting-started/docker-images.md).

# Docker Images

Terrakube publishes four images to Docker Hub. All are multi-architecture (`linux/amd64` and `linux/arm64`).

| Component          | Image                                                                              |
| ------------------ | ---------------------------------------------------------------------------------- |
| Terrakube API      | [`azbuilder/api-server`](https://hub.docker.com/r/azbuilder/api-server/tags)       |
| Terrakube Executor | [`azbuilder/executor`](https://hub.docker.com/r/azbuilder/executor/tags)           |
| Terrakube Registry | [`azbuilder/open-registry`](https://hub.docker.com/r/azbuilder/open-registry/tags) |
| Terrakube UI       | [`azbuilder/terrakube-ui`](https://hub.docker.com/r/azbuilder/terrakube-ui/tags)   |

### Tags

| Tag                | Meaning                                                                    |
| ------------------ | -------------------------------------------------------------------------- |
| `2.33.3`           | A release. Use an exact version in production.                             |
| `2.34.0-beta.10`   | A pre-release of the next version.                                         |
| `2.33.3-alpaquita` | The same release on Alpaquita Linux (API, executor and registry only).     |
| `latest`           | The newest build, which can be a pre-release. Do not use it in production. |

Run the API, executor, registry and UI at the **same version**. With the Helm chart set `api.version`, `executor.version`, `registry.version` and `ui.version`; see [Helm Chart](/2.34.0/getting-started/deployment/helm-chart.md#choose-the-terrakube-version) and [Upgrading](/2.34.0/getting-started/upgrading.md). To reproduce a deployment exactly, pin the image digest as well as the tag.

```bash
docker pull azbuilder/api-server:2.33.3
docker pull azbuilder/executor:2.33.3
docker pull azbuilder/open-registry:2.33.3
docker pull azbuilder/terrakube-ui:2.33.3
```

### How they are built

The default images are based on Ubuntu Jammy and are built with [Cloud Native Buildpacks](https://buildpacks.io/) through the Spring Boot Maven plugin, which is also how [custom CA certificates](/2.34.0/getting-started/deployment/custom-ca-certs.md) are added at runtime. The release pipeline also generates software bills of materials and pins base images by digest; see [Security](/2.34.0/how-it-works/security.md).

### Alpaquita Linux (experimental)

Every release also has API, executor and registry images based on [Alpaquita Linux](https://bell-sw.com/alpaquita-linux/), a smaller image built for Spring Boot. They use the same version with an `-alpaquita` suffix:

```bash
docker pull azbuilder/api-server:2.33.3-alpaquita
docker pull azbuilder/open-registry:2.33.3-alpaquita
docker pull azbuilder/executor:2.33.3-alpaquita
```

{% hint style="danger" %}
The Alpaquita **executor** image does not include Git, so Terraform modules that clone over Git during a run will not work, for example:

```hcl
module "consul" {
  source = "git@github.com:hashicorp/example.git"
}
```

{% endhint %}

### Use your own registry

To pull from a private mirror, copy the images and point the chart at them with `api.image`, `executor.image`, `registry.image` and `ui.image`, and add `global.imagePullSecrets` if the mirror needs credentials.


---

# 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.terrakube.io/2.34.0/getting-started/docker-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.