Table of Contents

Container Images

Payload image
Client payload image
Base image
GUI runtime image
Server image
Admin image
Client image
mRomexis Web App image
Migration and Control Agent images

Branch Image Suffixes
CI Staging Tags and Build Cache
Pulling Images
Runtime Compose Image References

Deutsch | English

Container Images

Images are published to the Gitea package registry namespace used by the project.

Main Images

gitea.buchhorster.de/planmeca/romexis-payload:<version>
gitea.buchhorster.de/planmeca/romexis-client-payload:<version>
gitea.buchhorster.de/planmeca/romexis-firebird-payload:latest

gitea.buchhorster.de/planmeca/romexis-base-jre:11-amd64
gitea.buchhorster.de/planmeca/romexis-base-jre:11-arm64
gitea.buchhorster.de/planmeca/romexis-base-jre:11

gitea.buchhorster.de/planmeca/romexis-gui-runtime:1-amd64
gitea.buchhorster.de/planmeca/romexis-gui-runtime:1-arm64
gitea.buchhorster.de/planmeca/romexis-gui-runtime:1

gitea.buchhorster.de/planmeca/romexis-server:<version>-amd64
gitea.buchhorster.de/planmeca/romexis-server:<version>-arm64
gitea.buchhorster.de/planmeca/romexis-server:<version>

gitea.buchhorster.de/planmeca/romexis-admin:<version>-amd64
gitea.buchhorster.de/planmeca/romexis-admin:<version>-arm64
gitea.buchhorster.de/planmeca/romexis-admin:<version>
gitea.buchhorster.de/planmeca/romexis-admin:latest

gitea.buchhorster.de/planmeca/romexis-client:<version>-amd64
gitea.buchhorster.de/planmeca/romexis-client:<version>-arm64
gitea.buchhorster.de/planmeca/romexis-client:<version>
gitea.buchhorster.de/planmeca/romexis-client:latest

gitea.buchhorster.de/planmeca/romexis-mromexis-app:<version>-amd64
gitea.buchhorster.de/planmeca/romexis-mromexis-app:<version>-arm64
gitea.buchhorster.de/planmeca/romexis-mromexis-app:<version>
gitea.buchhorster.de/planmeca/romexis-mromexis-app:latest

gitea.buchhorster.de/planmeca/romexis-migration-service:amd64
gitea.buchhorster.de/planmeca/romexis-migration-service:arm64
gitea.buchhorster.de/planmeca/romexis-migration-service:latest

gitea.buchhorster.de/planmeca/romexis-control-agent:amd64
gitea.buchhorster.de/planmeca/romexis-control-agent:arm64
gitea.buchhorster.de/planmeca/romexis-control-agent:latest

Tagging Strategy

Payload image

The Windows payload image is versioned by Romexis version and is architecture-independent:

romexis-payload:6.5.3.444.203

Client payload image

The Client payload is versioned independently from the final Client image but uses the same Romexis version:

romexis-client-payload:6.5.3.444.203

Base image

Base images are architecture-specific and also published as a manifest:

romexis-base-jre:11-amd64
romexis-base-jre:11-arm64
romexis-base-jre:11

GUI runtime image

Admin and Client share an architecture-specific GUI runtime that is also published as a multi-architecture manifest:

romexis-gui-runtime:1-amd64
romexis-gui-runtime:1-arm64
romexis-gui-runtime:1

Server image

Server images are architecture-specific and published as a multi-architecture manifest:

romexis-server:6.5.3.444.203-amd64
romexis-server:6.5.3.444.203-arm64
romexis-server:6.5.3.444.203

Admin image

The Admin image uses the Romexis payload and provides the browser/noVNC Admin runtime:

romexis-admin:<version>-amd64
romexis-admin:<version>-arm64
romexis-admin:<version>
romexis-admin:latest

Client image

The Client is a standalone final image and does not inherit from Admin:

romexis-client:<version>-amd64
romexis-client:<version>-arm64
romexis-client:<version>
romexis-client:latest

mRomexis Web App image

The mRomexis Web App image is versioned by Romexis version:

romexis-mromexis-app:<version>-amd64
romexis-mromexis-app:<version>-arm64
romexis-mromexis-app:<version>
romexis-mromexis-app:latest

It can only be built for Romexis versions that contain:

/opt/romexis/broker/mromexis-html.war

This is expected for Romexis 6.5.3 and newer.

Migration and Control Agent images

These services are independent from the Romexis installer version matrix and publish architecture aliases plus a latest multi-architecture manifest:

romexis-migration-service:amd64
romexis-migration-service:arm64
romexis-migration-service:latest

romexis-control-agent:amd64
romexis-control-agent:arm64
romexis-control-agent:latest

Branch Image Suffixes

For main, IMAGE_SUFFIX stays empty:

IMAGE_SUFFIX=

For feature branches, use a branch-specific suffix:

IMAGE_SUFFIX=-feature-romexis-admin

Example resolved image:

gitea.buchhorster.de/planmeca/romexis-server:6.5.3.444.203-feature-romexis-admin

This prevents feature branch builds from overwriting or being confused with main runtime images. Stable versioned payloads are normally reused without a branch suffix; only branches that change payload generation create isolated commit-specific CI payload tags.

CI Staging Tags and Build Cache

Drone does not build directly into public runtime tags. Architecture builds first use immutable commit-specific staging tags, for example:

romexis-base-jre:ci-<commit>-amd64
romexis-gui-runtime:ci-<commit>-arm64
romexis-server:ci-<commit>-<version>-amd64
romexis-admin:ci-<commit>-<version>-arm64
romexis-client:ci-<commit>-<version>-amd64

Only after both architectures succeed are public manifests updated with docker buildx imagetools create. Separate romexis-buildcache:* registry entries are BuildKit caches and are not runtime images.

Pulling Images

For multiarch usage:

docker pull gitea.buchhorster.de/planmeca/romexis-server:6.5.3.444.203

Admin image:

docker pull gitea.buchhorster.de/planmeca/romexis-admin:latest

Client image:

docker pull gitea.buchhorster.de/planmeca/romexis-client:latest

mRomexis Web App image:

docker pull gitea.buchhorster.de/planmeca/romexis-mromexis-app:6.5.3.444.203

Runtime Compose Image References

Compose uses manifest tags instead of architecture-specific tags:

${REGISTRY}/${ROMEXIS_IMAGE}:${ROMEXIS_VERSION}${IMAGE_SUFFIX}
${REGISTRY}/${MIGRATION_IMAGE}:latest${IMAGE_SUFFIX}
${REGISTRY}/${ADMINISTRATION_IMAGE}:latest${IMAGE_SUFFIX}
${REGISTRY}/${MROMEXIS_WEBAPP_IMAGE}:${ROMEXIS_VERSION}${IMAGE_SUFFIX}