$.Values.imageCredentials.registry value.
Prerequisites
- Access to download Thoras container images (email support@thoras.ai for assistance)
- A private container registry accessible from your Kubernetes cluster
- Container images pushed to your private registry
Configuration
Set the private registry hostname value in your Helmvalues.yaml:
Copying Multi-Platform Images
Thoras container images are built for multiple platforms (linux/amd64 and
linux/arm64) to support multiple CPU architectures. When copying images from
the Thoras registry to your private registry, it’s a good idea to preserve the
multi-platform manifest to ensure compatibility across different CPU
architectures.
Generate a list of images to copy
services, thoras-dashboard-v2,
thoras-forecast, nginx, timescaledb) as well as oauth2-proxy and httpd
(the dashboard auth sidecar and its init container) and kube-webhook-certgen
(webhook TLS, unless you use cert-manager). All are hosted on the Thoras
registry, so air-gapped installs only need to mirror from the Thoras registry.
No separate upstream mirror step is needed.
If you deploy with
helm template rather than helm install, set
featureFlags.enableLegacySecretSeeding: false in your values (see Legacy
secret seeding) and consider
cert-manager for webhook
TLS so no Helm
hook Jobs are involved.Using Docker Buildx
The recommended approach is to usedocker buildx imagetools create, which
preserves the multi-platform manifest. Substitute <VERSION> with the tag that
helm template shows for the release you’re deploying:
Verifying Multi-Platform Support
After copying, verify that both platforms are available:linux/amd64 and linux/arm64 in the output.

