Bundled Cube image (action required for some deployments)
From 6.0.2 and 5.4.5, the bundled service changes from upstreamcubejs/cube to
ghcr.io/formbricks/cube, initially 1.7.47-1. Use the image in your selected patch’s deployment files;
later image fixes are not automatically present in earlier releases.
The Formbricks image omits the shell, Python and Cube Store. Cube 1.7 returns numeric measures and
dimensions as strings; Formbricks normalizes them, but custom consumers of the Cube API must handle strings.
Docker and one-click
The updater preserves your customized Compose file. Replace the wholecube service: the new image
has no shell, so an old command: sh -c '…' wrapper fails with Cannot find module '/cube/conf/sh'.
-
From your existing Compose directory, download the selected release reference.
Back up your file with
cp -p docker-compose.yml docker-compose.yml.before-cube-image. -
In your editor, replace the
cube:block underservices:with the downloaded one, including its healthcheck and mounts. Keep yourCUBEJS_*secret and database overrides. Remove the old shell command. -
Download both model files from the same tag.
Validate and pull without restarting:
-
During your maintenance procedure, stop Cube, back up its model files
and install both files using the linked steps. After the required app/Hub migrations succeed:
Require a healthy container and working dashboard queries. If startup fails, inspect the logs and keep maintenance active. Confirm
CUBEJS_API_SECRETis present and the old shell wrapper is gone.
Helm and custom deployments
- Helm: the chart defaults to the new image. If your values set
cube.image.tagwithoutcube.image.repository, the chart now pulls a non-existentghcr.io/formbricks/cube:<your old tag>and the pod fails withImagePullBackOff. Drop the tag override, or set both values. Pointing them back at an upstreamcubejs/cuberelease is supported. - Helm security context: the Cube container now runs with a read-only root filesystem, no privilege
escalation and all capabilities dropped. The bundled image and upstream
cubejs/cubereleases need no change. A custom image or configuration that writes files, or dev mode on an upstream image, needscube.containerSecurityContext.readOnlyRootFilesystem: false. CUBEJS_DEV_MODE=true: not supported on the new image. Dev mode relies on the embedded Cube Store the image leaves out, so/readyzanswers 500 and the Helm probes and Compose healthcheck never pass. Leave it unset in production.- Air-gapped installs and registry mirrors: mirror the exact Cube image in your selected release’s Compose/chart along with the other
Formbricks images, then point the Compose
image:orcube.image.repositoryat your mirror.