Open CroccoRush opened 6 months ago
Linux kernel / udev is smart and knows how to discover USB cameras and interact with them driverlessly and puts them all under /dev/video. You should not normally have to manually configure discovery for the camera using serial or USB device hierarchies.
This device plugin by default discovers all cameras under /dev/usb and places groups them under the name squat.ai/video
. Indeed you can see that the plugin already discovered a camera for your node. Your node's description shows:
Allocatable:
...
squat.ai/video: 1
In fact the example in the readme for this project does exactly the same thing and uses squat.ai/video
to allocate a USB webcam for a pod: https://github.com/squat/generic-device-plugin?tab=readme-ov-file#overview
Please try using squat.ai/video
in your pod and let me know if that works for you.
Hello :)
I have the following problem: I want to access a USB camera inside my minikube pod. My env: Ubuntu 22.04, Minikube v1.32.0, Kubernetes v1.29.0
I am download
generic-device-plugin.yaml
to my computer and runkubectl apply -f=generic-device-plugin.yaml
. My node configuration after this looks like this:And
squat.ai/serial: 0
looks bad. I'm trying add-paths: - path: /dev/bus/usb/*/*/*
to a serial groups. After this I got:squat.ai/serial: 10
, but my camera doesn't throw inside pod.In the next step I try to connect the simple webcam and add
-paths: - path: /dev/video*
to a video groups. And that doesn't work either.