[GH-ISSUE #4] Emulator doesn't manage to boot in time in case of CI scenarios #3

New issue

Closed

opened 2026-03-01 15:39:05 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 15:39:05 +03:00

Owner

Originally created by @andrcuns on GitHub (May 15, 2017).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/4

In case if this container is used in some sort of CI setup for automated test execution, tests start executing before the android in emulator is actually booted up.
It is possible to delay test execution within test set up it self but would not be so convenient if deploying multiple containers with selenium grid via docker-compose for example.
Would You consider adding a check for avd boot_complete during container start?

Originally created by @andrcuns on GitHub (May 15, 2017). Original GitHub issue: https://github.com/budtmo/docker-android/issues/4 In case if this container is used in some sort of CI setup for automated test execution, tests start executing before the android in emulator is actually booted up. It is possible to delay test execution within test set up it self but would not be so convenient if deploying multiple containers with selenium grid via docker-compose for example. Would You consider adding a check for avd boot_complete during container start?

kerem

2026-03-01 15:39:05 +03:00

closed this issue
added the
help wanted
label

kerem commented

2026-03-01 15:39:06 +03:00

Author

Owner

@elgalu commented on GitHub (May 15, 2017):

SGTM 👍 What I do in docker-selenium is to

docker exec grid wait_all_done 10s

This will active wait up to 10 seconds for the container to be ready for tests but will finish as soon as is ready. This script can also be used as a HEALTHCHECK instruction.

So you guys could do something similar for this image, e.g.

docker exec android-container healthcheck.sh 1m

And inside that healthcheck.sh you put all the logic to wait for what's needed, avd boot_complete and so on.

So users can be sure that after that the container is ready to be used for testing.

@elgalu commented on GitHub (May 15, 2017): SGTM :+1: What [I do in docker-selenium](https://github.com/elgalu/docker-selenium) is to docker exec grid wait_all_done 10s This will active wait up to 10 seconds for the container to be ready for tests but will finish as soon as is ready. This script can also be used as a HEALTHCHECK instruction. So you guys could do something similar for this image, e.g. docker exec android-container healthcheck.sh 1m And inside that `healthcheck.sh` you put all the logic to wait for what's needed, avd boot_complete and so on. So users can be sure that after that the container is ready to be used for testing.

kerem commented

2026-03-01 15:39:07 +03:00

Author

Owner

@budtmo commented on GitHub (May 15, 2017):

could you maybe help me to fix this issue? @andrcuns

@budtmo commented on GitHub (May 15, 2017): could you maybe help me to fix this issue? @andrcuns

kerem commented

2026-03-01 15:39:07 +03:00

Author

Owner

@andrcuns commented on GitHub (May 15, 2017):

I have some ideas based on @elgalu excellent suggestion. I will try to test it out :)

@andrcuns commented on GitHub (May 15, 2017): I have some ideas based on @elgalu excellent suggestion. I will try to test it out :)

kerem commented

2026-03-01 15:39:07 +03:00

Author

Owner

@budtmo commented on GitHub (May 19, 2017):

I will close this PR, I have already included the implementation in release 0.5

@budtmo commented on GitHub (May 19, 2017): I will close this PR, I have already included the implementation in release [0.5](https://github.com/butomo1989/docker-android/releases/tag/0.5)

kerem referenced this issue

2026-03-01 15:39:07 +03:00

[GH-ISSUE #2] ChromeDriver not working #1