For the complete documentation index, see llms.txt. This page is also available as Markdown.

Docker Images

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

Component
Image

Terrakube Executor

Terrakube Registry

Tags

Tag
Meaning

2.34.0

A release. Use an exact version in production.

2.34.0-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 and Upgrading. To reproduce a deployment exactly, pin the image digest as well as the tag.

docker pull azbuilder/api-server:2.34.0
docker pull azbuilder/executor:2.34.0
docker pull azbuilder/open-registry:2.34.0
docker pull azbuilder/terrakube-ui:2.34.0

How they are built

The default images are based on Ubuntu Jammy and are built with Cloud Native Buildpacks through the Spring Boot Maven plugin, which is also how custom CA certificates are added at runtime. The release pipeline also generates software bills of materials and pins base images by digest; see Security.

Alpaquita Linux (experimental)

Every release also has API, executor and registry images based on Alpaquita Linux, a smaller image built for Spring Boot. They use the same version with an -alpaquita suffix:

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.

Last updated

Was this helpful?