This might not be an issue but its more of a discussion (PS. It would be nice to have a discussions page to ask questions)
I have already seen the advantages of bumble for my use cases which is emulating BLE GATT interfaces from Iot Device firmware for integration tests (e.g. a Linux BLE Gateway or a Phone application). As I really like to automate everything I was interested in doing integration tests within Docker.
However, to use docker container (linux) with Bluez as far as I know you need access to the Bluetooth from host PC, otherwise you will get the error
Can't open HCI socket.: Address family not supported by protocol
Which happens when Bluez opens an HCI socket [1].
For a practical solution I have found out that I need to set up for my CI/CD a runner (either Gitlab or Github) that has access to the Bluetooth host even though I am not going to use real hardware rather bumble to create a virtual hci.
So I was wondering if there is a way to have a real virtual bluetooth bluez driver running on docker to use bumble. Its not that big of a problem but I rather run everything virtually with default runners (spawned by Github or Gitlab) rather than having a dedicated server to run my virtual bluetooth integration tests.
This came to my thought in the sense that if bumble already allows virtualization of bluetooth why not in Bluez in Docker, somehow (?).
Thanks for reading, I come more from an Embedded background so I might be ignorant on virtual solutions for bluetooth. Open for suggestions.
This might not be an issue but its more of a discussion (PS. It would be nice to have a discussions page to ask questions)
I have already seen the advantages of bumble for my use cases which is emulating BLE GATT interfaces from Iot Device firmware for integration tests (e.g. a Linux BLE Gateway or a Phone application). As I really like to automate everything I was interested in doing integration tests within Docker.
However, to use docker container (linux) with Bluez as far as I know you need access to the Bluetooth from host PC, otherwise you will get the error
Can't open HCI socket.: Address family not supported by protocolWhich happens when Bluez opens an HCI socket [1].
For a practical solution I have found out that I need to set up for my CI/CD a runner (either Gitlab or Github) that has access to the Bluetooth host even though I am not going to use real hardware rather bumble to create a virtual hci.
So I was wondering if there is a way to have a real virtual bluetooth bluez driver running on docker to use bumble. Its not that big of a problem but I rather run everything virtually with default runners (spawned by Github or Gitlab) rather than having a dedicated server to run my virtual bluetooth integration tests.
This came to my thought in the sense that if bumble already allows virtualization of bluetooth why not in Bluez in Docker, somehow (?).
Thanks for reading, I come more from an Embedded background so I might be ignorant on virtual solutions for bluetooth. Open for suggestions.