Unable to install Chaos Mesh - Error Message - Error while dialing: dial unix /var/run/tw.runc.sock: connect: no such file or directory

[reubenrajan]

Helm Install output:

[arcos_*******_l2@bastian helm]$ oc logs chaos-controller-manager-59cc786644-jgcc7
failed to get create response: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial unix /var/run/tw.runc.sock: connect: no such file or directory"
exec /usr/local/bin/chaos-controller-manager: exec format error
[arcos_*******_l2@bastian helm]$

Context:
OCP, K8s 1.31, Chaos Mesh 1.27.2

[STRRL]

exec /usr/local/bin/chaos-controller-manager: exec format error

I am not sure you're using an ARM Kubernetes cluster, and Chaos Mesh does not support ARM now.

[reubenrajan]

These are amd64 nodes, and not ARM. I wasn't able to find any answers about what tw.runc.sock is. I understand it's the socket path.

While reviewing helm charts, i found out that ChaosMesh supports OCP/OCI -

| `chaosDaemon.runtime` | Runtime specifies which container runtime to use. Currently we only supports docker, containerd and CRI-O. | `docker` |
| `chaosDaemon.socketPath` | Specifiesthe path of container runtime socket on the host. | `/var/run/docker.sock` |

We are also seeing the same error when we tried to set the socketpath and daemon -

helm install chaos-mesh chaos-mesh -n=chaos-mesh --set images.registry=registry.*******.it --set chaosDaemon.socketpath=/var/run/crio/crio.sock --set chaosDaemon.runtime=crio

[reubenrajan]

Attaching the events log for better context.
events.txt