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.

helm output

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

Diagnose it: render the chart before you install it

Most Helm failures are visible in the rendered manifests. Template them locally with the same values CI uses and you will usually see the problem without touching the cluster.

Terminal

# what will actually be applied
helm template <release> <chart> -f values.ci.yaml | head -60

# validate against the live cluster schema without installing
helm install <release> <chart> -f values.ci.yaml --dry-run --debug

# what state is the release actually in?
helm history <release>
helm status <release>

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.

Terminal

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

Script helm repo add for each dependency at the start of the deploy step.
Cache ~/.config/helm between runs if you want to skip re-adding.
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

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

There are 2 common causes: no repos added on this runner and repo update before repo add. Helm’s repositories.yaml is empty/absent because the ephemeral runner never ran helm repo add.

How do I fix Helm "Error: no repositories found / no repositories to show" in CI?

There are 2 fixes depending on which cause you have: add the repo before updating or installing and make repo setup part of the job. Work through them in order, since the first is the most common.

What does Helm "Error: no repositories found / no repositories to show" in CI actually mean?

helm repo update fails with Error: no repositories found.

How do I stop Helm "Error: no repositories found / no repositories to show" in CI happening again?

Add required Helm repos at the top of the CI job, before update/search/install. The prevention section lists 3 changes that keep it from recurring.