Joe Borg

@talha0324 @liyoujunlizi That fixed the attacher issue, but I get ``` Warning FailedMount 5s (x9 over 2m13s) kubelet MountVolume.MountDevice failed for volume "pvc-de09f6fb-2280-4336-b482-e76fac582301" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient:...

@talha0324 I did: ``` pod/csi-attacher-s3-0 1/1 Running 0 30m pod/csi-provisioner-s3-0 2/2 Running 0 30m pod/csi-s3-9r4n7 2/2 Running 0 30m ``` ``` NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE csi-s3 ch.ctrox.csi.s3-driver Delete...

`kube-system`

@notDavid I've just tried this too but it doesn't fix the issue. If this is totally reliant on X11 libs, I think it's going to be a ground up remake...

Thanks for the reply @shivamerla, when removing `mountPropagation: Bidirectional` from `nvidia-container-toolkit-daemonset`, the following happens: ``` NAMESPACE NAME READY STATUS RESTARTS AGE kube-system pod/coredns-64c6478b6c-sckd6 1/1 Running 0 21m kube-system pod/calico-node-msfbm 1/1...

I was running this with `--set driver.enabled=false`, if I run on a fresh system with no drivers preinstalled and `--set driver.enabled=true`, I see ``` NAMESPACE NAME READY STATUS RESTARTS AGE...

I'd also appreciate a fix for this as Boxer always sets this icon when running (so you can't overwrite it from finder)

Hi there, Do you happen to be run this on a hybrid GPU (e.g. laptop combining intel and nvidia)?

Awesome, thanks for sharing that @klueska, I'll try it out.

So happy to see this go GA! Well done everyone.