-
-
Notifications
You must be signed in to change notification settings - Fork 228
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
Adb server freeze when run test in parallel in Docker for Mac + USB 2.0 controller #66
Comments
Hi @xuanzhaopeng , why do you need to have multiple containers? I think you can register multiple devices in one single container as long as devices are connected to the same machine. |
Hey @butomo1989 , just back from selenium conference, I will try your solution today |
Hey @butomo1989 @red-avtovo I figure it out based on : https://stackoverflow.com/questions/29563183/connecting-to-a-usb-android-device-in-a-docker-container-via-adb Besides, I upgrade docker from 17.02 to 17.09, and use USB 3.0 control in VirtualBox instead of USB 2.0 The adb server instance should have different port within multiple containers PS: @butomo1989 the reason why I use multiple containers because I want to create scalable selenium-node, and to make the log could be readable instead of mixed all sessions log into one |
I think we could keep this issue here, and for others who want to use appium-docker @saikrishna321 |
In my opinion we should move this issue to for example FAQ or something else in the readme/documentation if we won’t to work on this issue. |
@butomo1989 we should Document this |
Could you maybe help to move it to readme @xuanzhaopeng ? I think you can explain it in a better way. |
I just start this topic when you start one docker-machine with multiple appium-docker-android containers , and run test in parallel
I found adb server will freeze just after several run when u start test in multiple containers. However I cannot figure out the reason...
I'd like to know whether you guys maybe also found this problem.
PS: when u run test only in ONE container, it works perfect.
The text was updated successfully, but these errors were encountered: