Replies: 2 comments
-
The drivers wouldn't be much of a problem but the configuration would be more difficult. Especially since bluetooth is usually an interactive flow of scan, pair, accept which isn't possible through a declarative API. Sound drivers would likely be straightforward to add but I don't think we would want to run ALSA or pulse daemons on the system so you'd likely need to mount the device (privileged pod) and run the daemons or init system inside the pod itself. Unless there's a business case for these devices they're not going to be high on our priority list. Have you looked at our system extensions for adding drivers to Talos? https://github.com/siderolabs/extensions That's generally where this type of stuff would go. |
Beta Was this translation helpful? Give feedback.
-
Yeah, so i've managed to bypass the need of bluetooth, but it still would be great to have sound device drivers to utilize node's embedded sound system. There's nothing like this currently in the extensions repo... |
Beta Was this translation helpful? Give feedback.
-
Is there a way to use node's bluetooth adapter? I assume there's a need to install drivers and blues package somehow at least, and then pass /run/dbus to the pod (this is how I did it on k3s).
Second question is pretty much the same, but about sound device - previously I just passed /dev/snd to container, but with Talos I believe we need some drivers and pod with pulseaudio, or something...
I'm still new to Talos and its features, so please bear with me.
Beta Was this translation helpful? Give feedback.
All reactions