Container Registry

All images are distributed through the private Rulemapping Solutions container registry at registry.onstackit.cloud. Downloading image tarballs is no longer necessary.

Images

Image	Purpose
registry.onstackit.cloud/rms/ktdocker:3.24.28	The RAP application
registry.onstackit.cloud/rms/rmsaimiddlewaredocker:1.1.12	AI middleware (LLM gateway)

The tags above were current when this guide was written — use the versions issued for your installation.

Authentication

Rulemapping Solutions issues a dedicated robot account per installation and provides two values for it:

Value	Example	Notes
Account name	robot$rms+acme	contains a $ — see the warning below
Password	—	individual per installation, delivered separately from the name

Neither value is shared with any other installation. If they need to be replaced — a colleague left, the password ended up in a ticket — ask Rulemapping Solutions for a new pair; the previous one is revoked.

The $ in the robot name

The account name contains a $, which the shell would expand. Always wrap it in single quotes — double quotes are not enough.

Log in once on the host that runs the containers:

docker login registry.onstackit.cloud -u 'robot$rms+acme'

You are prompted for the password. To avoid the password appearing in your shell history, pipe it in instead:

read -rs ROBOT_PASSWORD
printf '%s' "$ROBOT_PASSWORD" \
  | docker login registry.onstackit.cloud -u 'robot$rms+acme' --password-stdin
unset ROBOT_PASSWORD

The credentials are stored base64-encoded in ~/.docker/config.json of the user who ran the command.

Pulling the images

Pull both images now, by their full name and explicit tag (shown with the tags from the table above). This works before the installation directory exists — the tags are the ones that will go into docker-compose.yml.

docker pull registry.onstackit.cloud/rms/ktdocker:3.24.28
docker pull registry.onstackit.cloud/rms/rmsaimiddlewaredocker:1.1.12

The application image is needed before the database can be set up: the SQL schema files are extracted from it, see Database.

docker images | grep onstackit

If the pull fails with unauthorized, the robot account has no permission for the repository — contact Rulemapping Solutions. If it fails with a network or TLS error, outbound HTTPS to registry.onstackit.cloud is not getting through.