-
Notifications
You must be signed in to change notification settings - Fork 159
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
Using noble within a docker container #43
Comments
I suspect problem in docker run params ? |
Thanks, these are the docker commands I'm using: docker build -t mqtt-server . My Dockerfile: `FROM node:latest WORKDIR specifies the directory our ` ` |
Is the problem in mqtt or noble module ? Maybe try to play along different network mode, I used: https://github.com/rzr/webthing-iotjs/blob/master/docker-compose.yml#L21 |
Thanks @rzr , Having done some more research, I think it's the bluetooth module in noble because I'm running docker locally on a mac but haven't found a solution so far? https://forums.docker.com/t/cannot-access-macbook-built-in-bluetooth-in-docker-debian-container/32819 Maybe it's not to do with noble |
Sorry I am a linux user but I can give a try, may you open a PR with docker-compose file running a sample self test and I'll try it and will share you logs |
Hello! As AcCalzone mentioned, I am running into the same phenomenon here AlCalzone/ioBroker.ble#422 (comment) I have closed it, as it does not seem to be an AlCalzone/BLE issue then. Any update on this here? |
Maybe this issue can be solved as I solved mine: Run the container with --net host rather than shared. Although this thread is pretty old, it may help others to find the own mistake as I did after several days? buanet/ioBroker.docker#134 (comment) |
feel free to add a chapter in readme file about using with docker |
Hi, did you run noble within a Docker container? |
I have developed my own npm package that depends on I am having a similar issue. Here is the error:
I am running Node-RED on RPi 4 that runs DietPi. |
Use |
This is indeed now written up in the README > Docker section: https://github.com/abandonware/noble/#docker Thanks to @atrovato ❤️ |
I am trying to use noble in a node (v13.8.0) app running in a local docker container.
When I run my application I receive the below error. It seems like there is an issue with hci-socket.
`/app/node_modules/@abandonware/noble/lib/hci-socket/hci.js:75
this._socket = new BluetoothHciSocket();
^
Error: EAFNOSUPPORT, Address family not supported by protocol
at new Hci (/app/node_modules/@abandonware/noble/lib/hci-socket/hci.js:75:18)
at new NobleBindings (/app/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:28:15)
at Object. (/app/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:511:18)
at Module._compile (internal/modules/cjs/loader.js:1151:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)
at Module.load (internal/modules/cjs/loader.js:1000:32)
at Function.Module._load (internal/modules/cjs/loader.js:899:14)
at Module.require (internal/modules/cjs/loader.js:1040:19)
at require (internal/modules/cjs/helpers.js:72:18)
at module.exports (/app/node_modules/@abandonware/noble/lib/resolve-bindings.js:13:12) {
errno: 97,
code: 'EAFNOSUPPORT',
syscall: 'socket'
}
`
I found this on noble noble#805
Does anyone have a workaround?
Thanks!
The text was updated successfully, but these errors were encountered: