# Docker Images

| Component          | Link                                                    |
| ------------------ | ------------------------------------------------------- |
| Terrakube API      | <https://hub.docker.com/r/azbuilder/api-server/tags>    |
| Terrakube Registry | <https://hub.docker.com/r/azbuilder/open-registry/tags> |
| Terrakube Executor | <https://hub.docker.com/r/azbuilder/executor/tags>      |
| Terrakube UI       | <https://hub.docker.com/r/azbuilder/terrakube-ui/tags>  |

{% hint style="success" %}
Default Images are based on Ubuntu Jammy (linux/amd64)
{% endhint %}

The docker images are generated using cloud native buildpacks with the maven plugin, more information can be found in these links:

* <https://docs.spring.io/spring-boot/docs/current/reference/html/container-images.html#container-images.buildpacks>
* <https://docs.spring.io/spring-boot/docs/3.1.5/maven-plugin/reference/htmlsingle/#build-image>

### Alpaquita Linux (Experimental)

From Terrakube 2.17.0 we generate 3 additional docker images for the API, Registry and Executor components that are based on [Alpaquita Linux](https://bell-sw.com/alpaquita-linux/) that are designed and optimized for Spring Boot applications.

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

{% hint style="danger" %}
Alpaquita Linux images for the Executor component does not include GIT, Terraform modules using remote executions like the following wont work:

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

{% endhint %}


---

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