Android Emulator can't start tests wait: http://172.18.0.4:4444/wd/hub does not respond. SOLVED

[BorisPotapov]

Hello,

I have the same question https://stackoverflow.com/questions/68915182/how-to-close-nested-virtualization-popup-for-emulator-while-running-automation-t

My tests can't start cause sees Nested Virtualization popup. (image default android 6.0) I downloaded https://github.com/aerokube/images then went so /selenium/ and started ./automate_android.sh with defaults

I got images android:8.1 then I added this to browser and started my tests

when I start this image Can't start test wait: http://172.18.0.4:4444/wd/hub Max time for waiting 20m

environment: win10 i7 +VirtBox Ubuntu 18 + testng + gradle

May be you can help me!

[vania-pooh]

@BorisPotapov should not be shown. https://github.com/aerokube/images/blob/master/selenium/android/Emulator.conf#L2

[BorisPotapov]

@vania-pooh thanks for fast answer.

I can't build image correctly with this emulator config. After build i see error in my test " wait: http://172.18.0.4:4444/wd/hub does not respond in 20m0s"

but if I started image what i downloaded by ./cm selenoid start --browser "android:6.0" this image start correctly (2 min) but I see Nested Virtualization popup

or you mean I should switch this parameter manually or when start my test? Please, send me example

[vania-pooh]

@BorisPotapov should build your image from scratch.

[BorisPotapov]

@vania-pooh could you send me steps for it, please. I am not sure that I can build image from scratch.

I see only this documentation "https://aerokube-com.translate.goog/images/latest/?_x_tr_sl=auto&_x_tr_tl=ru&_x_tr_hl=be#_building_images" and for creating android image i found two lines

$ cd selenium
$ ./automate_android.sh

I used they the previous time. this lines don't suite for my problem.

Interesting, I downloaded image from this repo budim/selenoid-android:11.0-no-google and got the same problem

If you send me more information i will appreciate

[BorisPotapov]

@vania-pooh I have idea.

Perhaps, this example https://github.com/aerokube/images was created without Enable Nested Virtualization because it is the same problem like I solved when installed Virtual Box to Win10.

I mean maybe default android images hasn't this config https://github.com/aerokube/images/blob/master/selenium/android/Emulator.conf#L2 and start correctly, but this example https://github.com/aerokube/images has this conf and haven't Enable Nested Virtualization true.

What about this idea?

[vania-pooh]

@BorisPotapov older images in Docker hub don't have this config.

[BorisPotapov]

@vania-pooh I build image with showNestedWarning=true and this image start works correctly like older images. I see this Nested Virtualization popup.

Now I am sure that showNestedWarning=false works with some problems for my configuration VirtBox Ubuntu 18 + android image for win10.

[BorisPotapov]

I did it.

I just rewrote showNestedWarning=false without spaces and rebuilt the image and it worked for me.

[vania-pooh]

@BorisPotapov don't get how you fixed it.

[BorisPotapov]

@vania-pooh I deleted extra spaces at the end of this file Emulator.conf :)

and the image was built correctly

[vania-pooh]

@BorisPotapov closing then?

[BorisPotapov]

@vania-pooh yes, please :)

[BorisPotapov]

@vania-pooh May be need to delete extra spaces at the end of https://github.com/aerokube/images/blob/master/selenium/android/Emulator.conf#L2 too.

[vania-pooh]

@BorisPotapov I don't see such spaces in raw file version. Probably that's a Windows BOM symbol.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.