Docker Images

Workloads would be running as containers in Airbase. As such, applications would need to be built as Docker images to be deployed on Airbase.

Managed Images

Airbase provide base images for popular languages that should be used to maximize deployment compatibility.

For most languages, there would be 2 variants provided:

base: Base image which should be used as the “final” image that would be used to run your application.
builder: Builder image with SEED certificate trusted. This image should be used for local development builds, or as intermediate images used during multi-stage builds to retrieve application dependencies.

Managed images are built provided as multi-arch images, supporting both linux/amd64 and linux/arm64.

See for Managed Base Images for available images.

Images will only be tagged with the major version.
Images will be periodically rebuilt on [day of the week], that would update all the OS dependencies.

Managed images are hosted on Docker Hub and SGTS Gitlab Container Registry (GLCR).

To avoid running into Docker Hub pull limits, consider using the SGTS GLCR images in your CI builds.

SGTS GLCR images are prefixed with registry.sgts.gitlab-dedicated.com/innersource/sgts/runtime/airbase/images

Example

Docker Hub Image: gdssingapore/airbase:node-22
SGTS Mirror: registry.sgts.gitlab-dedicated.com/innersource/sgts/runtime/airbase/images/gdssingapore/airbase:node-22

You can also use your own base images if you wish. However, there may be some additional configuration that you should include in your images.

See Custom Images for more information.