failed to "StartContainer" for "intel-gpu-initcontainer

andre181723

Cadet
Joined
Aug 24, 2022
Messages
1
Hello,

After switching from CORE 12 to SCALE (using the upgrade file TrueNAS-SCALE-22.02.3.update), the following messages are being logged:

Code:
Aug 24 09:49:12 nas1 k3s[4553]: {"level":"warn","ts":"2022-08-24T09:49:12.498-0700","logger":"etcd-client","caller":"v3@v3.5.1-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc001500fc0/kine.sock","attempt":0,"error":"rpc error: code = Unknown desc = no such table: dbstat"}
Aug 24 09:49:15 nas1 k3s[4553]: E0824 09:49:15.702379    4553 pod_workers.go:949] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"intel-gpu-initcontainer\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=intel-gpu-initcontainer pod=intel-gpu-plugin-xhqcm_kube-system(b8b81901-82fa-4ca5-ae5f-06d756483221)\"" pod="kube-system/intel-gpu-plugin-xhqcm" podUID=b8b81901-82fa-4ca5-ae5f-06d756483221
Aug 24 09:49:27 nas1 k3s[4553]: E0824 09:49:27.701972    4553 pod_workers.go:949] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"intel-gpu-initcontainer\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=intel-gpu-initcontainer pod=intel-gpu-plugin-xhqcm_kube-system(b8b81901-82fa-4ca5-ae5f-06d756483221)\"" pod="kube-system/intel-gpu-plugin-xhqcm" podUID=b8b81901-82fa-4ca5-ae5f-06d756483221
Aug 24 09:49:38 nas1 k3s[4553]: E0824 09:49:38.702776    4553 pod_workers.go:949] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"intel-gpu-initcontainer\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=intel-gpu-initcontainer pod=intel-gpu-plugin-xhqcm_kube-system(b8b81901-82fa-4ca5-ae5f-06d756483221)\"" pod="kube-system/intel-gpu-plugin-xhqcm" podUID=b8b81901-82fa-4ca5-ae5f-06d756483221


This is on an old computer, so I guess it might be missing something only available on newer systems:
Intel® Core™2 Duo E6300
Intel® Desktop Board DG965SS

I'd like to use KVM, but don't really care about losing Docker and Kubernetes.

I tried deleting intel/intel-gpu-initcontainer:0.19.0 from Apps > Docker Images, but the following error is shown:
DockerError(409, 'conflict: unable to delete e026ae0f49c4 (must be forced) - image is being used by stopped container 3641a31be6a6')

Is there a way to fix or just disable whatever is causing this?
 
Top