0xEmma
Cadet
- Joined
- Oct 18, 2021
- Messages
- 8
Trying to setup apps, however it seem the k3s cluster backing it refuses to ever start up, with all the pods in kube-system resulting in a crashloop, causing any installed apps to not work due to nodes being tainted as not ready.
Ive tried unsetting pool, restarting, deleting ix-applications, all without any luck, the only logs ive managed to gather for information are as follows, which makes it seems like the CSI socks are failing.
and "journalctl -fu k3s" giving
System Info:
Server: D51PH-1ULH
CPU: E5-2620v4
RAM: 128gb ECC DDR3 2166mhz

Ive tried unsetting pool, restarting, deleting ix-applications, all without any luck, the only logs ive managed to gather for information are as follows, which makes it seems like the CSI socks are failing.
and "journalctl -fu k3s" giving
Any ideas on what im doing wrong here so i can get it to work?33096 remote_runtime.go:479] "ExecSync cmd from runtime service failed" err="rpc error: code = Unknown desc = failed to exec in container: failed to start exec \"1e7db503acc30ba9c102950d9c2153ed59d068f44ce0b495aa1c864999df51e2\": OCI runtime exec failed: exec failed: unable to start container process: exec: \"/bin/sh\": stat /bin/sh: no such file or directory: unknown" containerID="dc292607f8d55a32d676d65e1f5ac6002f28ab29a2ed49ae679af2e76fee75c1" cmd=[/bin/sh -c rm -rf /registration/zfs-localpv /registration/zfs-localpv-reg.sock]
System Info:
Server: D51PH-1ULH
CPU: E5-2620v4
RAM: 128gb ECC DDR3 2166mhz