Skip to content

Bluetooth adapter not found in docker container #1307

Closed Answered by Ripper346
Ripper346 asked this question in Q&A
Discussion options

You must be logged in to vote

So, apparently using killall -9 bluetoothd doesn't do much, it kills the bluetooth service but then for a Raspberry card the service is triggered again to open. This caused the bluetooth card to be busy and so being invisible for bluez inside the docker container. I was able to disable the bluetooth service in the OS, and bluez and consequently bleak, started working. Sorry for the trouble, in the end it wasn't even related to bleak

Replies: 2 comments 5 replies

Comment options

You must be logged in to vote
5 replies
@Ripper346
Comment options

@Ripper346
Comment options

@dlech
Comment options

@Ripper346
Comment options

@Ripper346
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by Ripper346
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #1306 on May 10, 2023 13:35.