I have used the project from the Readme.md and I am trying to execute the docker command that runs those tests, to achieve that I have changed the following command from the Readme.md: docker run -it -rm -v $PWD /android-testing/ui /espresso/ BasicSample: /root/tmp budtmo /docker-android-x86-8.1 tmp/gradlew build Hello, I am trying to set up Docker-Android to run Espresso tests. The behavior is like the behavior when starting the container in docker run.
The health status in docker is health: starting and the logs do not go further. When I execute it with docker-compose up I get`the following output: Creating network "docker_default" with the default driverĪndroid-client | 2019- 05- 07 06: 19: 46, 979 CRIT Supervisor running as root (no user in config file)Īndroid-client | 2019- 05- 07 06: 19: 46, 981 INFO supervisord started with pid 8Īndroid-client | 2019- 05- 07 06: 19: 47, 983 INFO spawned: 'xvfb' with pid 11Īndroid-client | 2019- 05- 07 06: 19: 47, 983 INFO spawned: 'port-forward' with pid 12Īndroid-client | 2019- 05- 07 06: 19: 47, 985 INFO spawned: 'novnc' with pid 13Īndroid-client | 2019- 05- 07 06: 19: 47, 986 INFO spawned: 'openbox' with pid 14Īndroid-client | 2019- 05- 07 06: 19: 47, 987 INFO spawned: 'x11vnc' with pid 15Īndroid-client | 2019- 05- 07 06: 19: 47, 988 INFO spawned: 'android-screen-mirror' with pid 16Īndroid-client | 2019- 05- 07 06: 19: 47, 989 INFO spawned: 'docker-appium' with pid 17Īndroid-client | 2019- 05- 07 06: 19: 47, 991 INFO spawned: 'auto-recording' with pid 26Īndroid-client | 2019- 05- 07 06: 19: 47, 992 INFO spawned: 'adb-utils' with pid 29Īndroid-client | 2019- 05- 07 06: 19: 47, 993 INFO success: android-screen-mirror entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)Īndroid-client | 2019- 05- 07 06: 19: 47, 994 INFO exited: android-screen-mirror (exit status 0 expected)Īndroid-client | 2019- 05- 07 06: 19: 48, 993 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)Īndroid-client | 2019- 05- 07 06: 19: 48, 993 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)Īndroid-client | 2019- 05- 07 06: 19: 48, 993 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)Īndroid-client | 2019- 05- 07 06: 19: 48, 993 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)Īndroid-client | 2019- 05- 07 06: 19: 48, 993 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)Īndroid-client | 2019- 05- 07 06: 19: 48, 993 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)Īndroid-client | 2019- 05- 07 06: 19: 48, 993 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)Īndroid-client | 2019- 05- 07 06: 19: 48, 993 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)Īndroid-client | 2019- 05- 07 06: 19: 49, 024 INFO exited: docker-appium (exit status 1 not expected)Īndroid-client | 2019- 05- 07 06: 19: 53, 998 INFO exited: auto-recording (exit status 0 expected)
But you see opt which is where you were before.Hey all, did someone of you tried to run the emulator out of docker compose? Its not working for me with this file: version: '3' You can see that /android-sdk-linux/toolsdoes not exist if you ls the root directory ls / Without the leading /, which signifies the root directory right at the top. When you have completed the previous commands you are still in the directory /opt and android-sdk-linux is a subdirectory of it, and tools is a subdirectory of android-sdk-linux, so you cd to it like this: cd android-sdk-linux/tools
0 kommentar(er)
