Unable to mount volumes var-lib-rancher, etc-ssl, ...

[toriaezunama]

I have just installed the kim client on my linux NUC and ran ./kim builder install --selector k3s.io/hostname=<rpi-hostname> against my k3s RPI cluster.

The builder pod is getting stuck in the ContainerCreating state as you can see from kubectl get pods,services -n kube-image

NAME                READY   STATUS              RESTARTS   AGE
pod/builder-7vl46   0/2     ContainerCreating   0          5m11s
NAME              TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                         AGE
service/builder   NodePort   10.43.233.104   <none>        1234:32016/TCP,1233:30724/TCP   5m11s

The details from running kubectl describe pods -n kube-image are as follows:

...snip...
Events:
  Type     Reason       Age                   From               Message
  ----     ------       ----                  ----               -------
  Normal   Scheduled    7m9s                  default-scheduler  Successfully assigned kube-image/builder-7vl46 to rpi-107
  Warning  FailedMount  5m7s                  kubelet            Unable to attach or mount volumes: unmounted volumes=[var-lib-buildkit], unattached volumes=[var-lib-rancher etc-ssl tls-ca tls-server tmp run etc-pki cgroup var-lib-buildkit default-token-fnnlk]: timed out waiting for the condition
  Warning  FailedMount  2m50s                 kubelet            Unable to attach or mount volumes: unmounted volumes=[var-lib-buildkit], unattached volumes=[var-lib-rancher etc-pki run var-lib-buildkit tls-server default-token-fnnlk tmp etc-ssl cgroup tls-ca]: timed out waiting for the condition
  Warning  FailedMount  58s (x11 over 7m10s)  kubelet            MountVolume.SetUp failed for volume "var-lib-buildkit" : hostPath type check failed: /var/lib/buildkit is not a directory
  Warning  FailedMount  35s                   kubelet            Unable to attach or mount volumes: unmounted volumes=[var-lib-buildkit], unattached volumes=[run etc-pki cgroup var-lib-buildkit var-lib-rancher default-token-fnnlk tmp tls-server etc-ssl tls-ca]: timed out waiting for the condition

@dweomer Mentioned that this is likely "an oversight in my daemonset spec"

[dweomer]

From the slack convo: I am realizing that I didnt build/push arm64 images (or a manifested image at all).

[dweomer]

The v0.1.0-alpha.9 release may address the underlying issue(s) here.

[dweomer]

@toriaezunama from our slack convo I believe that the multi-arch release did finally address this. Please re-open if such is not the case.

[toriaezunama]

It did thanks