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

Why "BtleJuice Proxy does not work in a Docker container." #48

Open
erdnussflips opened this issue Jan 13, 2019 · 2 comments
Open

Why "BtleJuice Proxy does not work in a Docker container." #48

erdnussflips opened this issue Jan 13, 2019 · 2 comments

Comments

@erdnussflips
Copy link

erdnussflips commented Jan 13, 2019

Could anyone explain me, why this not work in a Docker container?

@nathanloop
Copy link

nathanloop commented Nov 15, 2019

The reason you can't use both roles of Btlejuice on one machine is how the Linux kernel handles the Bluetooth adapters. It can only support one.

Docker containers use the host kernel, so two docker containers have the same host kernel. You're going to run into the same issue as a single machine host. With VMs you have two kernels, so the one physical machine can support multiple adapters.

@aolszowka
Copy link

I know this is old; but FWIW based on the comments from @nathanloop the "does not work in a docker container" comment was intended to indicate that you could not run both on the same machine.

For my purposes I have two machines:

  1. To run the proxy that is close to the device in question
  2. To run the console

Because of this I reasoned that I should be able to create containers and run them on both machines to target their needs. I have done so and created this public repository https://github.com/aolszowka/docker-btlejuice. It seems to be working for the most part for my usage, as of this writing the images aren't optimized, but at least they work.

HUGE thank you for this tool!

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

3 participants