Fluent bit installation fails from Private Harbor registry with error "vendir: Error: Syncing directory '0':" and Get "https://projects.registry.vmware.com/v2/": dial tcp ######: i/o timeout
search cancel

Fluent bit installation fails from Private Harbor registry with error "vendir: Error: Syncing directory '0':" and Get "https://projects.registry.vmware.com/v2/": dial tcp ######: i/o timeout

book

Article ID: 429684

calendar_today

Updated On:

Products

VMware vSphere Kubernetes Service

Issue/Introduction

Installing fluent bit from Private Harbor fails

 

kubectl get pods -n tanzu-system-logging
NAME                READY   STATUS             RESTARTS   AGE
fluent-bit-######   0/1     ImagePullBackOff   0          3d21h
fluent-bit-######   0/1     ImagePullBackOff   0          3d21h

 

k describe pod fluent-bit-xxxxx -n tanzu-system-logging

Containers:
  fluent-bit:
    Container ID:   
    Image:          #############/standard/repo/v2025.6.18@sha256:######

 Warning  Failed   2m20s (x565 over 3d2h)   kubelet  Failed to pull image 

 

k get pkgi -A |grep fluent

NAMESPACE              NAME                             PACKAGE NAME                          PACKAGE VERSION                DESCRIPTION                  
fluent-bit-######      fluent-bit-######                fluent-bit.tanzu.vmware.com           2.2.3+vmware.1-tkg.2           Reconcile failed: Error

 

k describe pkgi fluent-bit-######  -n fluent-bit-######

  Useful Error Message:    vendir: Error: Syncing directory '0':
  Syncing directory '.' with imgpkgBundle contents:
    Fetching image:
      Error while preparing a transport to talk with the registry:
        Unable to create round tripper:
          Get "https://projects.registry.vmware.com/v2/": dial tcp  ######:443: i/o timeout

 

Confirm which standard package is available in Private Harbor

tanzu package repository list -A

NAMESPACE   NAME            SOURCE                                          STATUS              
tkg-system  tanzu-standard  ############/packages/standard/repo:v2025.6.18  Reconcile succeeded 

 

 

Environment

vSphere 8.0U3

Cause

Standard package available in Private Harbor (here v2025.6.18) is not compatible with VKS (Note: it is a package compatible with TKG)

see compatible standard packages: VKS Standard Packages Release Notes

Resolution

Upload a compatible VKS standard package to the Harbor following Push Standard Packages to a Private Harbor