# SOLO-5095

> KindClusterContainerNotFoundSoloError — System

URL: https://solo.hiero.org/docs/troubleshooting/errors/system/SOLO-5095/

| | |
|---|---|
| **Code** | `SOLO-5095` |
| **Category** | System |
| **Ownership** | User |
| **Retryable** | No |

## Description

Thrown by the `solo cluster-ref state` commands when the container engine is reachable but there is no Kind cluster node container (a container carrying the `io.x-k8s.kind.cluster` label) for Solo to start, stop, or report on — either none exists at all, or none of the ones that exist are mapped to a Solo cluster reference. Typically the cluster was never created, was deleted (`kind delete cluster`), or was never connected to Solo.

## Troubleshooting Steps

1. List existing Kind clusters: kind get clusters
1. List the clusters Solo manages: solo cluster-ref config list
1. Map an existing cluster to Solo: solo cluster-ref config connect --cluster-ref <name> --context kind-<cluster>
1. Create a cluster with a full deployment: solo one-shot single deploy
