Skip to content
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

RPi3: working locally but not in Docker #1

Open
jelalanne opened this issue Dec 4, 2019 · 1 comment
Open

RPi3: working locally but not in Docker #1

jelalanne opened this issue Dec 4, 2019 · 1 comment

Comments

@jelalanne
Copy link

Hello, your scan sample is working on my raspberry Pi perfectly, but not in a Docker container. I can detect the Bluetooth chip with adapter hci0 as seen on below screenshot (so I know I have enough privilege for the container to access the chip), but the cs program doesn't seem to find it (i'm running the app through a dockerfile, in an Azure IoT Edge context).
image

Even when I run GetAdaptersAsync(), with another error:
image

uname -a:
image

Dockerfile:
image

Launch script:
image

Thanks for your help!

@jelalanne
Copy link
Author

jelalanne commented Dec 5, 2019

Ok, so i've managed to make it, just by manually stopping/starting bluetoothd just before starting dotnet module. If anyone has an explanation, I would be grateful!
image

jamesra pushed a commit to jamesra/DotNet-BlueZ that referenced this issue Apr 19, 2022
Add Connect device function to Adapter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant