EIB Image creation fails regularily on OpenShift

[jomeier]

Hi,
I run EIB version 1.2.1 on OpenShift and rather often it fails with this error message:

2025-08-26T09:00:19.205Z        INFO    log/audit.go:62 Setting up Podman API listener...
2025-08-26T09:00:19.207Z        INFO    podman/listener.go:59   Waiting for '/run/podman/podman.sock' to be created
2025-08-26T09:00:19.207Z        INFO    podman/listener.go:66   '/run/podman/podman.sock' file is not yet created, retrying in 3 seconds
2025-08-26T09:00:22.210Z        INFO    podman/listener.go:62   '/run/podman/podman.sock' file has been created successfully
2025-08-26T09:00:22.285Z        FATAL   build/build.go:88       An error occurred building the image: building combustion: initialising embedded artifact registry: storing helm charts: downloading chart: adding repo: exit status 1
github.com/suse-edge/edge-image-builder/pkg/cli/build.Run
        /home/abuild/rpmbuild/BUILD/edge-image-builder-1.2.1/pkg/cli/build/build.go:88
github.com/urfave/cli/v2.(*Command).Run
        /home/abuild/rpmbuild/BUILD/edge-image-builder-1.2.1/vendor/github.com/urfave/cli/v2/command.go:276
github.com/urfave/cli/v2.(*Command).Run
        /home/abuild/rpmbuild/BUILD/edge-image-builder-1.2.1/vendor/github.com/urfave/cli/v2/command.go:269
github.com/urfave/cli/v2.(*App).RunContext
        /home/abuild/rpmbuild/BUILD/edge-image-builder-1.2.1/vendor/github.com/urfave/cli/v2/app.go:333
github.com/urfave/cli/v2.(*App).Run
        /home/abuild/rpmbuild/BUILD/edge-image-builder-1.2.1/vendor/github.com/urfave/cli/v2/app.go:307
main.main
        /home/abuild/rpmbuild/BUILD/edge-image-builder-1.2.1/cmd/eib/main.go:20
runtime.main
        /usr/lib64/go/1.24/src/runtime/proc.go:283

I gave the pod plenty of resources in my Gitlab CI pipeline:
KUBERNETES_CPU_REQUEST: "5"
KUBERNETES_CPU_LIMIT: "5"
KUBERNETES_MEMORY_REQUEST: "16Gi"
KUBERNETES_MEMORY_LIMIT: "32Gi"

If I retry often enough, it works.

Does anybody have a good idea? If I start it on a linux shell it seems to work always.

[atanasdinov]

From the logs it sounds like this is a failure on helm add repo. Are you able to find the corresponding Helm log file?