Jan Pazdziora

I don't think the code in local-path-provisioner does much with setting up the root fs and the mount points for the pod. This seems to be related to how the...

Ah, you meant if there is something wrong about that specific example? Not really, when I turn it into a trivial busybox container with ``` apiVersion: v1 kind: Pod metadata:...

I only saw it with that helper pod. When I apply a pod without any volumes ``` apiVersion: v1 kind: Pod metadata: name: no-volume spec: containers: - name: no-volume image:...

To debug, when I ``` kubectl edit -n local-path-storage cm local-path-config ``` and change `image` to `busybox` and add a `mount` and `sleep` to `setup` with ``` helperPod.yaml: |- apiVersion:...

Thanks for that pointer -- I confirm that when I add ``` securityContext: privileged: true ``` to my regular container, I get the same issues as with the local-path helper....

Well realistically I'd be OK to just disable any propagation of `/dev/bus/usb` to the containers, either the first one (`podman`), or the next layer (`containerd`?). Is the search for the...

So with some experimentation, I got the setup working with ```diff --- a/images/base/files/etc/containerd/config.toml +++ b/images/base/files/etc/containerd/config.toml @@ -19,6 +19,9 @@ version = 2 runtime_type = "io.containerd.runc.v2" # Generated by "ctr oci...

Ah, great. I confirm that with ``` kind: Cluster apiVersion: kind.x-k8s.io/v1alpha4 nodes: - role: control-plane [...] containerdConfigPatches: - |- [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc] privileged_without_host_devices = true ``` things work just fine. I'm closing...

I confirm that with ``` kind: Cluster apiVersion: kind.x-k8s.io/v1alpha4 nodes: - role: control-plane extraMounts: - hostPath: /dev containerPath: /dev ``` the problem is gone as well. After the removal of...

> I am using an updated version of the binary firmware. It improves my C20v5... @ggbruno Would you have some pointer to the description of using the binary firmware, especially...