[BUG] Failed to pulll image

[mchudinov]

📋 Prerequisites

• I have searched the existing issues to avoid creating a duplicate
• By submitting this issue, you agree to follow our Code of Conduct
• I am using the latest version of the software
• I have tried to clear cache/cookies or used incognito mode (if ui-related)
• I can consistently reproduce this issue

🎯 Affected Service(s)

Multiple services / System-wide issue

🚦 Impact/Severity

No impact (Default)

🐛 Bug Description

kagent deployments in Kubernetes Failed to pull image.
Kubernetes v 1.34.3 running on Windows desktop WSL2 kind

Example:
Failed to pull image "cr.kagent.dev/kagent-dev/kagent/ui:0.9.1": failed to pull and unpack image "cr.kagent.dev/kagent-dev/kagent/ui:0.9.1": short read: expected 1609 bytes but got 0: unexpected EOF

Failed to pull image "cr.kagent.dev/kagent-dev/kagent/app:0.9.0": failed to pull and unpack image "cr.kagent.dev/kagent-dev/kagent/app:0.9.0": short read: expected 1609 bytes but got 0: unexpected EOF

Same issue for kagent v 0.9.0 and v 0.9.1

Some parts of kagent work well like kagent-controller, kagent-postgresql, kagent-grafana-mcp

🔄 Steps To Reproduce

1. Enable Kubernetes in Docker desktop on Windows. Use kind confoguration, enable WSL2 Docker engine v29.4.0
2. Run Ubuntu WSL2, install brew on it.
3. Install kagent CLI tool using brew in Ubuntu WSL2
4. Install kagent to Kubernetes cluster

🤔 Expected Behavior

All deployments of kagent must download Docker images and run.

📱 Actual Behavior

Many kagent deployments can not download Docker images.

• helm-agent
• cilium-debug-agent
• istio-agent
• kagent-ui

💻 Environment

No response

🔧 CLI Bug Report

No response

🔍 Additional Context

No response

📋 Logs

📷 Screenshots

No response

🙋 Are you willing to contribute?

• I am willing to submit a PR to fix this issue