Container images

The backend and frontend are separate images. Use the tested pair from the same server release.

Images and architectures

The release workflow builds linux/amd64 and linux/arm64. Backend artifacts include Node and Bun runtime variants.

Find a release pair

Open GitHub releases and choose a server release, not a userscript release.

The *-dockerhub-image.txt and *-ghcr-image.txt assets contain immutable image references. Use both references from one release and registry. If no server release is available, build with Docker.

Pair tags include both app versions, such as backend-1.2.3-frontend-4.5.6. That is a format example, not a version to copy.

Use the images

Set the references in .env:

CAELESTIS_BACKEND_IMAGE=replace-with-the-backend-image-reference
CAELESTIS_FRONTEND_IMAGE=replace-with-the-frontend-image-reference

With your usual Compose file list, run:

docker compose pull
docker compose up -d --no-build --wait

The --no-build flag uses the configured images instead of building the checkout. Include your database and storage overlays as described in Docker Compose stacks.

Container settings

These are Caelestis images, not LinuxServer.io images. They do not use PUID or PGID configuration.

Before changing versions, follow Deployment and upgrades.