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
No /dev/bus/usb virtualization on Mac OS Sierra #8
Comments
Unfortunately Docker on Mac does not support USB, since the underlying xhyve doesn't support it. The old boot2docker may have worked by tweaking VM settings. I think the easiest (perhaps only?) way to get it to work would be to use a Linux VM and run docker there instead. |
When you are talking about xhyve, are you talking about Hypervisor.Framework? Veertu uses this as well and seems to support USB. Maybe things did change in the meantime? Having this working on Mac OS Sierra would be very very great because I don't have to install Java into the host system. |
Please let me know if that's the case and we can update the instructions.
…On Fri, Mar 17, 2017 at 1:28 Tobias Tom ***@***.***> wrote:
When you are talking about xhyve, are you talking about
Hypervisor.Framework? Veertu uses this as well and seems to support USB.
Maybe things did change in the meantime?
Having this working on Mac OS Sierra would be very very great because I
don't have to install Java into the host system.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB-_TLF0kKn1t-vzFRxhDl33yWPbpqPks5rmWNHgaJpZM4KNzO8>
.
|
I'm very glad to help here, but unfortunately I have no idea how to confirm it. A linux inside a Virtual machine can see the device with Any recommendations on how to debug it? |
Try gaining access to the tiny vm docker for mac uses, see if it's there at
least.
…On Fri, Mar 17, 2017 at 2:07 Tobias Tom ***@***.***> wrote:
I'm very glad to help here, but unfortunately I have no idea how to
confirm it.
A linux inside a Virtual machine can see the device with adb device.
docker-adb can't on the same host system.
Any recommendations on how to debug it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB-_XXvq4TBo67IjU8Su3xPo4Wsh-jBks5rmWwugaJpZM4KNzO8>
.
|
Stopping the machine, enabling USB manually in the VirtualBox interface (the machine is based on VirtualBox), and starting it again makes the device appear in
Removing the device will result in this result:
Unfortunately
|
I don't follow 100%, are you saying that you're modifying the Docker for
Mac xhyve vm with VirtualBox? Or a separate VM?
Also, I would suggest sharing actual docker run commands instead of
docker-compose. Hard to tell what options you are using.
…On Fri, Mar 17, 2017 at 2:31 Tobias Tom ***@***.***> wrote:
Stopping the machine, enabling USB manually in the VirtualBox interface
(the machine is based on VirtualBox), and starting it again makes the
device appear in lsusb when plugged in:
$ docker-compose run adbd lsusb -v
Bus 001 Device 002: ID 18d1:4ee2
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
Removing the device will result in this result:
$ docker-compose run adbd lsusb -v
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
Unfortunately adb devices is not able to see it:
$ docker-compose run adbd adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB-_Xpi7rbS_fuwsbT8XkrFOnompzdMks5rmXHVgaJpZM4KNzO8>
.
|
the adb devices is not working in 2nd containers . only works in one container |
That's how it works. Only one adb server can be online at the same time.
You should link to that container in order to run commands in other
containers.
…On Fri, Jul 21, 2017 at 13:34 swaroopbalan ***@***.***> wrote:
the adb devices is not working in 2nd containers . only works in one
container
ALl devices are taken by the first container
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB-_aBQX2gGpKl9TZaPnET5ckVtm-Peks5sQCpbgaJpZM4KNzO8>
.
|
thanks for the response .. docker run -it -h basispost101l --name 'basispost101l' -d --privileged -v /dev/bus/usb:/dev/bus/usb --device=/dev/ttyACM0:/dev/ttyRelayCard -p 5001:22 testbench /bin/bash |
I want adb to show all devices in all containers |
Closing, since this is more of a Docker for Mac issue. |
As mentioned above, using Linux VM seems to the only way. |
What is the situation now? I have the same problem,I don't know how to solve it |
Hi, I am adding a way to solve this as it is indeed a Mac OS issue and not a docker adb issue.
You can connect wirelessly to your device through adb. The way to achieve it is :
If you see and unauthorized device, try these commands to fix the issue :
I hope that will help some people. |
Anyone else with the same problem?
Without the device's virtual representation, how can I forward it to docker??
Thanks!
The text was updated successfully, but these errors were encountered: