SJ
I am using selenoid/android:9.0 image
I am using below command to start selenoid
./cm selenoid start --vnc --browsers "android:9.0" --args "-session-attempt-timeout 4m -service-startup-timeout 4m"
Size: a a a
2020 June 27
SJ
SJ
@vaniaPooh @aandryashin when i run the below command
docker run -d --name android-test -e ENABLE_VNC=true --privileged -p 4444:4444 -p 5900:5900 selenoid/android:9.0
In this case, the appium server is getting started. But the smae is not happening when the container is start from selenoid
docker run -d --name android-test -e ENABLE_VNC=true --privileged -p 4444:4444 -p 5900:5900 selenoid/android:9.0
In this case, the appium server is getting started. But the smae is not happening when the container is start from selenoid
SJ
IK
Sunil Jaiswal
@vaniaPooh @aandryashin when i run the below command
docker run -d --name android-test -e ENABLE_VNC=true --privileged -p 4444:4444 -p 5900:5900 selenoid/android:9.0
In this case, the appium server is getting started. But the smae is not happening when the container is start from selenoid
docker run -d --name android-test -e ENABLE_VNC=true --privileged -p 4444:4444 -p 5900:5900 selenoid/android:9.0
In this case, the appium server is getting started. But the smae is not happening when the container is start from selenoid
is it starting fast?
SJ
is it starting fast?
Yes
IK
could you try to add
enableVNC = true capability when running through SelenoidIK
there is a known bug in emulator in headless mode
IK
or add ENABLE_VNC=true environment variable in browsers.json
SJ
./cm selenoid start --vnc --browsers "android:9.0" --args "-session-attempt-timeout 4m -service-startup-timeout 4m" > over here?
IK
first try to run the same docker command without ENABLE_VNC env variable
IK
if it starts slowly, then add --browser-env "ENABLE_VNC=true" at the end of CM command
SJ
first try to run the same docker command without ENABLE_VNC env variable
Ok..will try this
SJ
@vaniaPooh what is the minimum memory requirement to run android image
IK
Sunil Jaiswal
@vaniaPooh what is the minimum memory requirement to run android image
something near 2 Gb per container
SJ
something near 2 Gb per container
Ok. Thanks... I think the issue with my system is because of memory.
SJ
If i reboot the machince and start, the appium is geeting started, however i am getting another issue
An unknown server-side error occurred while processing the command. Original error: Failed to launch Appium Settings app: Condition unmet after 8136 ms. Timing out.
An unknown server-side error occurred while processing the command. Original error: Failed to launch Appium Settings app: Condition unmet after 8136 ms. Timing out.
IK
Sunil Jaiswal
If i reboot the machince and start, the appium is geeting started, however i am getting another issue
An unknown server-side error occurred while processing the command. Original error: Failed to launch Appium Settings app: Condition unmet after 8136 ms. Timing out.
An unknown server-side error occurred while processing the command. Original error: Failed to launch Appium Settings app: Condition unmet after 8136 ms. Timing out.
seeing such message for the first time
SJ
seeing such message for the first time
😅 Currently i am doing a poc for running android using docker, hence didn't thought that memory will play such an important role. Will try to increase the memory and try the same again
SJ
Thanks a lot for all the help