> ## Documentation Index
> Fetch the complete documentation index at: https://formbricks.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 5.4.5 / 6.0.2: Cube image migration

> Apply the complete Cube service change when crossing 5.4.5 or 6.0.2.

**Introduced in:** 5.4.5 and 6.0.2 on their respective release lines.
**Applies to:** deployments using the bundled Cube service.

## Bundled Cube image (action required for some deployments)

From **6.0.2** and **5.4.5**, the bundled service changes from upstream `cubejs/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 **whole** `cube` service: the new image
has no shell, so an old `command: sh -c '…'` wrapper fails with `Cannot find module '/cube/conf/sh'`.

1. From your existing Compose directory, [download the selected release reference](https://formbricks.com/docs/self-hosting/upgrade/configuration.md#download-the-selected-release).
   Back up your file with `cp -p docker-compose.yml docker-compose.yml.before-cube-image`.

2. In your editor, replace the `cube:` block under `services:` with the downloaded one, including its
   healthcheck and mounts. Keep your `CUBEJS_*` secret and database overrides. Remove the old shell command.

3. [Download both model files](https://formbricks.com/docs/self-hosting/upgrade/configuration.md#download-the-cube-model-files) from the same tag.
   Validate and pull without restarting:

   ```bash theme={null}
   docker compose config --quiet && docker compose pull cube
   ```

4. During your [maintenance procedure](https://formbricks.com/docs/self-hosting/advanced/upgrade.md), stop Cube, back up its model files
   and install both files using the linked steps. After the required app/Hub migrations succeed:

   ```bash theme={null}
   docker compose up -d --no-deps --force-recreate cube
   docker compose ps cube
   docker compose logs --tail=100 cube
   ```

   Require a healthy container and working dashboard queries. If startup fails, inspect the logs and
   keep maintenance active. Confirm `CUBEJS_API_SECRET` is 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.tag` without
  `cube.image.repository`, the chart now pulls a non-existent `ghcr.io/formbricks/cube:<your old tag>` and the
  pod fails with `ImagePullBackOff`. Drop the tag override, or set both values. Pointing them back at an upstream
  `cubejs/cube` release 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/cube` releases need no change.
  A custom image or configuration that writes files, or dev mode on an upstream image, needs
  `cube.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 `/readyz` answers 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:` or `cube.image.repository` at your mirror.

To undo only the Cube service change, restore its previous configuration, image and matching model files,
then recreate Cube. This does not undo application or Hub migrations; use coordinated recovery for a full rollback.

## After

Confirm Cube is healthy, dashboard queries work, and both model files match the selected Formbricks release.
Keep prior configuration and model files together for recovery; a new image with an old shell command fails to start.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.