-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ble extension #247
Comments
You should be able to just attach a device (per Plug in the USB adapter, check the ID by using |
I don't think so. Bluetooth needs Kernelmodules. And i need Dbus to run. |
Any ideas? I have a container with priviledged, all caps, host network and mounted dbus, it still shows no BLE
Im assuming it goes to /dev but im unable to find out where In a privileged pod (only dbus mounted)
and
|
I'm believe for using bluetooth with talos you will have to build your own kernel (see https://www.talos.dev/v1.6/advanced/customizing-the-kernel/) with relevant kernel config parameters enabled (see e.g. https://github.com/torvalds/linux/blob/master/net/bluetooth/Kconfig). I've also found some articles about running the BlueZ daemon inside a pod (e.g. https://medium.com/omi-uulm/how-to-run-containerized-bluetooth-applications-with-bluez-dced9ab767f6). |
If/when talos gains the ability to load kernel modules signed with keys other then those generated (and thrown away) building the kernel it would also be possible to build a kernel with bluetooth as modules and package those in a talos system extension I think. |
There is also an issue on pkgs already. |
I know it’s a very niche thing. But for days I’m trying to get one of my Nodes to provision a matter-device. Bluetooth is needed during the comissioning-process. Would be great if Ble could be provided via an extension. Nevertheless thanks for this great and stable operating system.
The text was updated successfully, but these errors were encountered: