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

> Engine and metadata image tag overrides for the firebolt-instance Helm chart, including pinning a specific build.

# Image overrides

This page shows how to override the default engine and metadata image tags.

By default, the chart pulls engine and metadata from `ghcr.io/firebolt-db/{engine,metadata}` based on the `appVersion` in `Chart.yaml`.

## Track 'dev' images

To follow current-of-mainline builds, you can use the `dev` tag.

```yaml theme={"theme":{"light":"css-variables","dark":"css-variables"}}
engineSpec:
  image:
    tag: dev
metadata:
  image:
    tag: dev
```

The `dev` tag is mutable. Two installs minutes apart can pull different content. Pin the tag to a specific version for reproducible installs.

## Use a specific build

You can override the tag per component, but you must keep the version used for the Engine and used for the Metadata Service in [lockstep](##Lockstep).
You can choose the smaller `release-` versions or use the `debug-` prefix which contains debug symbols.

```yaml theme={"theme":{"light":"css-variables","dark":"css-variables"}}
engineSpec:
  image:
    tag: release-4.32.0-pre.0.20260609145613.22a1ea4abadb
metadata:
  image:
    tag: release-4.32.0-pre.0.20260609145613.22a1ea4abadb
```

## Lockstep

Engine and metadata ship from the same build pipeline and are not version-tolerant of each other. The chart does not enforce lockstep. Mismatched tags surface as a metadata-RPC failure at engine startup.