⚠️ Homebrew support is being deprecated. Solo will stop publishing updates to Homebrew after August 31, 2026. Install via npm install -g @hiero-ledger/solo@latest instead. See System Readiness for full install instructions.

SOLO-5079

KindClusterStoppedError — System

KindClusterStoppedError

CodeSOLO-5079
CategorySystem
OwnershipInfrastructure
RetryableYes

Description

Thrown when a kind cluster’s node container was found stopped, solo started it again, and the cluster’s Kubernetes API still did not answer; the last API failure is wrapped in cause. A kind node that restarts but never serves its API usually means the cluster did not survive whatever stopped it — the host was rebooted and the node’s networking or storage no longer lines up, the container is crash-looping, or the kubeconfig entry now points at a port the restarted node no longer listens on. It is retryable because a control plane can simply need longer than solo waited.

Troubleshooting Steps

  1. Check the node container is running: docker ps -a –filter name=-control-plane
  2. Inspect why the node is not serving its API: docker logs -control-plane
  3. Verify the cluster answers: kubectl cluster-info –context kind-
  4. Recreate the cluster if it did not survive being stopped: kind delete cluster –name