[Bug]: experimental.deploy.vcluster.helm.chart[].repo not deploying charts from OCI registries

[tylerauerbeck]

What happened?

Not sure if this is better for this repo or https://github.com/loft-sh/vcluster instead, so feel free to point me elsewhere if this isn't the appropriate repo.

I'm currently trying to spin up a VinD cluster and use the experimental.deploy.vcluster.helm configuration objects to deploy a handful of helm charts out of the box. A few of the charts I'm working with are OCI registries, is I would expect that for repo I would be able to supply (for example): oci://docker.io/envoyproxy/gateway-helm.

However, after supplying the config and deploying with vcluster create gateway --driver docker -f vcluster.yaml the cluster successfully spins up, but the helm charts are never deployed. I also do not see anything in the logs of the vind docker container mentioning that anything has gone wrong.

What did you expect to happen?

Like with other charts that I deploy from http/https endpoints, I would expect the charts to being begin deployed once the cluster is available. If there is a failure deploying the charts, I would expect some line saying that it was unable to deploy the chart successfully.

How can we reproduce it (as minimally and precisely as possible)?

Use the attached vcluster config, vcluster version 0.32.0

vCluster config

Details

experimental:
  docker:
    enabled: true

  deploy:
    vcluster:
      helm:
        - chart:
            name: gateway-helm
            version: v1.5.9
            repo: oci://docker.io/envoyproxy/gateway-helm
          release:
            name: envoy-gateway
            namespace: envoy-gateway-system
        - chart:
            name: gateway-crds-helm
            version: v1.5.9
            repo: oci://docker.io/envoyproxy/gateway-crds-helm
          release:
            name: envoy-gateway-crds
            namespace: envoy-gateway-system
          values: |-
            crds:
              gatewayAPI:
                enabled: true
                channel: standard
              envoyGateway:
                enabled: true

vCluster and Docker version

Details

$ vcluster --version
vcluster version 0.32.0

$ docker version
Client: Docker Engine - Community
 Version:           29.2.1
 API version:       1.53
 Go version:        go1.25.6
 Git commit:        a5c7197d72
 Built:             Mon Feb  2 16:33:58 2026
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.61.0 (219004)
 Engine:
  Version:          29.2.1
  API version:      1.53 (minimum version 1.44)
  Go version:       go1.25.6
  Git commit:       6bc6209
  Built:            Mon Feb  2 17:16:47 2026
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          v2.2.1
  GitCommit:        dea7da592f5d1d2b7755e3a161be07f43fad8f75
 runc:
  Version:          1.3.4
  GitCommit:        v1.3.4-0-gd6d73eb8
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ uname -a
Darwin Kernel Version 25.3.0: Wed Jan 28 20:53:31 PST 2026; root:xnu-12377.81.4~5/RELEASE_ARM64_T8122 arm64

Operating System

macOS (Apple Silicon)

Using vCluster Platform UI?

No - not using Platform UI

Relevant logs

Anything else we need to know?

No response

[janekbaraniewski]

Hey @tylerauerbeck!

The issue here is with your repo format.

       - chart:
            name: gateway-helm
            version: v1.5.9
            repo: oci://docker.io/envoyproxy/gateway-helm
          release:
            name: envoy-gateway
            namespace: envoy-gateway-system

repo field is a repository root and name is the name of specific chart you want to install. so your configuration actually results in

helm pull oci://docker.io/envoyproxy/gateway-helm/gateway-helm

which fails. fix here is to change your vcluster.yaml to

       - chart:
            name: gateway-helm
            version: v1.5.9
            repo: oci://docker.io/envoyproxy
          release:
            name: envoy-gateway
            namespace: envoy-gateway-system