What are the common problems in building Docker of win10 system
This article mainly explains "what are the common problems in the construction of win10 system Docker". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what are the common problems in the construction of win10 system Docker?"
Common problems encountered:
1.Unhandled rejection Error: spawn adb ENOENT
Adb problem. Restart stf after adb is set.
Not recognized by 2.Ubuntu device
Reason: USB bridge connection settings, above 2.0
Setting method: click Virtual Machine-"Settings -" USB Controller-"USB compatibility -" USB2.0
3.adb authorization failed
Reconnect to adb, or reconnect to adb after rebooting your phone
4. Cannot access the address, or remind you after starting provider: device (s) ignore, because there is a problem with the port configuration. Please check the virtual machine port mapping configuration and restart.
Ports that must be mapped: 7100, 28015, 7114, 7116, 7111, 7113, 7110, 7400, 7408, 7412, 7416,7420,7424,7428,7105,7112,7120,7104,7103,7102,7106,7115,7125,27017,5000 (optional, login authorization) Background Statistics Management) configuration method: edit-"Virtual Machine Network Editor -" change configuration-select vmnet8- "net setting -" add-"enter virtual machine ip (Ubuntu linux ip), host port and virtual machine port.
5 remind this socket has been ended by the other party
Reason: Port problem (have encountered adb port occupation, kill the service that occupies the port, restart).
6. The device status always shows the problem in preparation
In most cases, it is STFServer installation or startup failure. Install it manually (apk is in the project (root directory\ vendor\ STFService), or look for STFService.apk in soft), enter the startup service command: adb shell am start-n jp.co.cyberagent.stf/.IdentityActivityadb shell am startservice-n jp.co.cyberagent.stf/.Service
Stf api request occupies device and removes device interface debug address and parameters:
1. Device add Interface:
Address: http://${ local IP address or domain name. Modify / api/v1/user/devices request method: post request parameters: headers = {"Authorization": "Bearer ${token added in the stf setting, modify by yourself}"} body = {"serial": "91ccecd"} result: {"success": true, "description": "Device successfully added"} stf platform display interface status changed to bus
two。 Device removal interface: request parameter
Address: http://${ local IP address or domain name. Modify} / api/v1/user/devices? {serial} request method: delete request parameters: headers = {"Authorization": "Bearer ${token added in the stf setting, modify by yourself}"} result: {"success": true, "description": "Device successfully removed"} stf platform display interface status changed to use
Note: the IP address should be changed to the deployment environment address, and the auth3 login authorization service should be started first.
Thank you for your reading. The above is the content of "what are the common problems in the construction of win10 system Docker?" after the study of this article, I believe you have a deeper understanding of the common problems in the construction of win10 system Docker, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!
