Helm "Error: no repositories found / no repositories to show" in CI

By Kaveh Alemi·Latchkey

Helm keeps its list of added repositories in a per-user config file. On a fresh CI runner that file does not exist, so helm repo update, helm search repo, or any repo-dependent command has no repositories to work with.

What this error means

helm repo update fails with Error: no repositories found. You must add one before updating, or helm search repo <x> returns Error: no repositories to show. The runner simply has no repos configured yet.

Error: no repositories found. You must add one before updating

Common causes

No repos added on this runner

Helm’s repositories.yaml is empty/absent because the ephemeral runner never ran helm repo add. Repo state does not persist across fresh CI environments.

Repo update before repo add

A pipeline runs helm repo update (or a search/install from a named repo) before adding the repository it needs.

How to fix it

Add the repo before updating or installing

Add every repo the deploy needs, then update the index.

helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo update
helm install my-release bitnami/nginx

Make repo setup part of the job

1. Script helm repo add for each dependency at the start of the deploy step.
2. Cache ~/.config/helm between runs if you want to skip re-adding.
3. For OCI charts, no repo add is needed - reference oci:// directly.

How to prevent it

• Add required Helm repos at the top of the CI job, before update/search/install.
• Cache the Helm config dir or use oci:// references to avoid repo state.
• Do not assume repo config persists across ephemeral runners.

Frequently asked questions

Related guides

References

• Kubernetes documentation
• GitHub Actions documentation