starred/docker-android
1
0
Fork 0
mirror of https://github.com/budtmo/docker-android.git synced 2026-04-25 12:15:52 +03:00
Code Issues 21 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #195] Emulator hangs on loading screen #138

New issue
Open
opened 2026-03-01 15:40:49 +03:00 by kerem · 8 comments
kerem commented 2026-03-01 15:40:49 +03:00
Owner
Copy link

Originally created by @mcopjan on GitHub (Aug 28, 2019).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/195

🐛 Bug Report

Operating System:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

Docker Image:
budtmo/docker-android-x86-9.0

Docker Version:
Docker version 18.09.5, build e8ff056

Docker Command to start docker-android:

docker run --privileged -d -p 6080:6080 -p 4723:4723 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S10" -e APPIUM=true -e CONNECT_TO_GRID=true -e APPIUM_HOST="xxx.xxx.xxx.xx" -e APPIUM_PORT=4723 -e SELENIUM_HOST="xxx.xxx.xxx.xx" -e SELENIUM_PORT=4444 -e MOBILE_WEB_TEST=true -e RELAXED_SECURITY=true --name android-container budtmo/docker-android-x86-9.0

Expected Behavior

Emulator loads properly and device home page is displayed

Actual Behavior

Emulator is stuck on Google loading screen

Logs

martinc@ubuntu:~/bin$ docker exec -it android-container tail -f /var/log/supervisor/docker-android.stdout.log

  • Check "Android Emulator" checkbox
  • Click "OK"

emulator: No acpi ini file provided, using default

emulator: onGuestSendCommand: [0x8ef2800] Adb connected, start proxing data
emulator: _hwFingerprint_connect: connect finger print listen is called

emulator: got message from guest system fingerprint HAL

image

Originally created by @mcopjan on GitHub (Aug 28, 2019). Original GitHub issue: https://github.com/budtmo/docker-android/issues/195 ## 🐛 Bug Report Operating System: Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic Docker Image: budtmo/docker-android-x86-9.0 Docker Version: Docker version 18.09.5, build e8ff056 Docker Command to start docker-android: docker run --privileged -d -p 6080:6080 -p 4723:4723 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S10" -e APPIUM=true -e CONNECT_TO_GRID=true -e APPIUM_HOST="xxx.xxx.xxx.xx" -e APPIUM_PORT=4723 -e SELENIUM_HOST="xxx.xxx.xxx.xx" -e SELENIUM_PORT=4444 -e MOBILE_WEB_TEST=true -e RELAXED_SECURITY=true --name android-container budtmo/docker-android-x86-9.0 ## Expected Behavior Emulator loads properly and device home page is displayed ## Actual Behavior Emulator is stuck on Google loading screen ## Logs martinc@ubuntu:~/bin$ docker exec -it android-container tail -f /var/log/supervisor/docker-android.stdout.log - Check "Android Emulator" checkbox - Click "OK" emulator: No acpi ini file provided, using default emulator: onGuestSendCommand: [0x8ef2800] Adb connected, start proxing data emulator: _hwFingerprint_connect: connect finger print listen is called emulator: got message from guest system fingerprint HAL ![image](https://user-images.githubusercontent.com/20699180/63864941-98fe4480-c9a8-11e9-9ed2-e74b7618de23.png)
kerem commented 2026-03-01 15:40:50 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Sep 11, 2019):

Hi @mcopjan,

could you share your machine spec?

<!-- gh-comment-id:530319573 --> @budtmo commented on GitHub (Sep 11, 2019): Hi @mcopjan, could you share your machine spec?
kerem commented 2026-03-01 15:40:50 +03:00
Author
Owner
Copy link

@mcopjan commented on GitHub (Sep 11, 2019):

@budtmo
Ubuntu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 2
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 94
Model name: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Stepping: 3
CPU MHz: 2601.000
BogoMIPS: 5202.00
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
NUMA node0 CPU(s): 0,1

image

<!-- gh-comment-id:530355256 --> @mcopjan commented on GitHub (Sep 11, 2019): @budtmo Ubuntu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 2 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 94 Model name: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Stepping: 3 CPU MHz: 2601.000 BogoMIPS: 5202.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 6144K NUMA node0 CPU(s): 0,1 ![image](https://user-images.githubusercontent.com/20699180/64696695-fe692f80-d496-11e9-8e21-1021c8dfc7b0.png)
kerem commented 2026-03-01 15:40:50 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Oct 22, 2019):

is this issue still valid? @mcopjan

<!-- gh-comment-id:544845762 --> @budtmo commented on GitHub (Oct 22, 2019): is this issue still valid? @mcopjan
kerem commented 2026-03-01 15:40:51 +03:00
Author
Owner
Copy link

@mateleshkavo commented on GitHub (Nov 11, 2019):

@budtmo I have the same problem when launching docker images with 9.0 and 10.0 Android versions in the Kubernetes cluster. Here are my specs:
spec: containers: - env: - name: APPIUM value: "true" - name: APPIUM_HOST valueFrom: fieldRef: fieldPath: status.podIP - name: CONNECT_TO_GRID value: "true" - name: SELENIUM_HOST value: "xxx.xxx.xx.xx" - name: SELENIUM_PORT value: "30208" - name: MOBILE_WEB_TEST value: "true" - name: "BROWSER" value: "chrome" - name: "DEVICE" value: "Samsung Galaxy S10" image: "budtmo/docker-android-x86-10.0" name: android8-appium ports: - containerPort: 6080 securityContext: privileged: true resources: requests: memory: "2Gi" cpu: "3" limits: memory: "4Gi" cpu: "4" nodeSelector: beta.kubernetes.io/os: linux
Android 8.1 and earlier works fine.
VM OS is CentOS 7.7

<!-- gh-comment-id:552487124 --> @mateleshkavo commented on GitHub (Nov 11, 2019): @budtmo I have the same problem when launching docker images with 9.0 and 10.0 Android versions in the Kubernetes cluster. Here are my specs: `spec: containers: - env: - name: APPIUM value: "true" - name: APPIUM_HOST valueFrom: fieldRef: fieldPath: status.podIP - name: CONNECT_TO_GRID value: "true" - name: SELENIUM_HOST value: "xxx.xxx.xx.xx" - name: SELENIUM_PORT value: "30208" - name: MOBILE_WEB_TEST value: "true" - name: "BROWSER" value: "chrome" - name: "DEVICE" value: "Samsung Galaxy S10" image: "budtmo/docker-android-x86-10.0" name: android8-appium ports: - containerPort: 6080 securityContext: privileged: true resources: requests: memory: "2Gi" cpu: "3" limits: memory: "4Gi" cpu: "4" nodeSelector: beta.kubernetes.io/os: linux` Android 8.1 and earlier works fine. VM OS is CentOS 7.7
kerem commented 2026-03-01 15:40:51 +03:00
Author
Owner
Copy link

@mcopjan commented on GitHub (Nov 25, 2019):

is this issue still valid? @mcopjan

Hi @budtmo, yes this is still the issue. I tried on different Linux VM as well (Centos) with the following compose file

services:
  selenium_hub:
    image: selenium/hub
    restart: unless-stopped
    ports:
      - "4444:4444"

  emulator:
    image: budtmo/docker-android-x86-9.0
    restart: unless-stopped
    privileged: true
    depends_on:
      - selenium_hub
    ports:
      - 6080
      - 5554
      - 5555
    environment:
      - DEVICE=Samsung Galaxy S10
      - CONNECT_TO_GRID=True
      - APPIUM=true
      - SELENIUM_HOST=selenium_hub
      - MOBILE_WEB_TEST=true

and having the same problem as reported above. Interestingly as @mateleshkavo mentioned, the same compose file with version 8.1 works fine. Any idea? I wonder how people are using version 9.0 & 10.0

<!-- gh-comment-id:558062908 --> @mcopjan commented on GitHub (Nov 25, 2019): > is this issue still valid? @mcopjan Hi @budtmo, yes this is still the issue. I tried on different Linux VM as well (Centos) with the following compose file ``` services: selenium_hub: image: selenium/hub restart: unless-stopped ports: - "4444:4444" emulator: image: budtmo/docker-android-x86-9.0 restart: unless-stopped privileged: true depends_on: - selenium_hub ports: - 6080 - 5554 - 5555 environment: - DEVICE=Samsung Galaxy S10 - CONNECT_TO_GRID=True - APPIUM=true - SELENIUM_HOST=selenium_hub - MOBILE_WEB_TEST=true ``` and having the same problem as reported above. Interestingly as @mateleshkavo mentioned, the same compose file with version 8.1 works fine. Any idea? I wonder how people are using version 9.0 & 10.0
kerem commented 2026-03-01 15:40:51 +03:00
Author
Owner
Copy link

@mcopjan commented on GitHub (Nov 25, 2019):

When running with version 10.0

[root@uiplinfdoc019 martinco]# docker exec -it aa5c8 tail -f /var/log/supervisor/docker-android.stdout.log
 - Check "Android Emulator" checkbox
 - Click "OK"

emulator: No acpi ini file provided, using default

emulator: VERBOSE: winsys-qt.cpp:892: config multidisplay with config.ini 0x0 0x0 0x0
emulator: _hwFingerprint_connect: connect finger print listen is called

emulator: got message from guest system fingerprint HAL

^C[root@uiplinfdoc019 martinco]# ^C
[root@uiplinfdoc019 martinco]# docker exec -it aa5c8 tail -f /var/log/supervisor/docker-android.stderr.log
Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
pulseaudio: pa_context_connect() failed
pulseaudio: Reason: Connection refused
pulseaudio: Failed to initialize PA contextaudio: Could not init `pa' audio driver
Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
<!-- gh-comment-id:558075533 --> @mcopjan commented on GitHub (Nov 25, 2019): When running with version 10.0 ``` [root@uiplinfdoc019 martinco]# docker exec -it aa5c8 tail -f /var/log/supervisor/docker-android.stdout.log - Check "Android Emulator" checkbox - Click "OK" emulator: No acpi ini file provided, using default emulator: VERBOSE: winsys-qt.cpp:892: config multidisplay with config.ini 0x0 0x0 0x0 emulator: _hwFingerprint_connect: connect finger print listen is called emulator: got message from guest system fingerprint HAL ^C[root@uiplinfdoc019 martinco]# ^C [root@uiplinfdoc019 martinco]# docker exec -it aa5c8 tail -f /var/log/supervisor/docker-android.stderr.log Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null)) Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null)) Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null)) Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null)) Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null)) Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null)) pulseaudio: pa_context_connect() failed pulseaudio: Reason: Connection refused pulseaudio: Failed to initialize PA contextaudio: Could not init `pa' audio driver Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null)) ```
kerem commented 2026-03-01 15:40:51 +03:00
Author
Owner
Copy link

@NoelOmo commented on GitHub (Jan 21, 2020):

Any update on this issue? Did you find a workaround solution?

<!-- gh-comment-id:576687458 --> @NoelOmo commented on GitHub (Jan 21, 2020): Any update on this issue? Did you find a workaround solution?
kerem commented 2026-03-01 15:40:51 +03:00
Author
Owner
Copy link

@mcopjan commented on GitHub (Mar 16, 2020):

@NoelOmo yes, it is still an issue. I can spin up emulators for versions 7.1.1 and 8.1 but when I am using them with Appium to run tests I am getting "chromedriver is not reachable" error. I was hoping this would be resolved by using higher versions 9.0 or 10.0 (with higher version of chromedriver) but they exhibit the behaviour described above.

@budtmo any thoughts please? Do you have any HowTo build custom image with specific version of Chrome browser, chromedriver and Appium please?

<!-- gh-comment-id:599569612 --> @mcopjan commented on GitHub (Mar 16, 2020): @NoelOmo yes, it is still an issue. I can spin up emulators for versions 7.1.1 and 8.1 but when I am using them with Appium to run tests I am getting "chromedriver is not reachable" error. I was hoping this would be resolved by using higher versions 9.0 or 10.0 (with higher version of chromedriver) but they exhibit the behaviour described above. @budtmo any thoughts please? Do you have any HowTo build custom image with specific version of Chrome browser, chromedriver and Appium please?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v3.3.0-p0
v3.2.2-p0
v3.2.0-p0
v3.1.1-p0
v3.1.0-p0
v3.0.2-p2
v3.0.2-p1
v3.0.2-p0
v3.0.1-p1
v3.0.1-p0
v2.19.0-p2
v2.19.0-p1
v2.19.0-p0
v2.18.0-p0
v2.16.2-p0
v2.15.0-p1
v2.15.0-p0
v2.11.4-p0
v2.11.2-p0
v2.11.1-p0
v2.5.4-p1
v2.5.4-p0
v2.5.1-p0
v2.5.0-p0
v2.4.1-p0
v2.3.0-p1
v2.3.0-p0
v2.2.2-p0
v2.1.3-p1
v2.1.3-p0
v2.0.1-p1
v2.0.0-p6
v2.0-p5
v2.0-p4
v2.0-p3
v2.0-p2
v2.0-p1
v1.10-p7
v1.10-p6
v1.10-p5
v1.10-p4
v1.10-p3
v1.10-p2
v1.10-p1
v1.9-p8
v1.9-p7
v1.9-p6
v1.9-p5
1.9-p4
1.9-p3
1.9-p2
1.9-p1
1.9-p0
1.8-p16
1.8-p15
1.8-p14
1.8-p13
1.8-p12
1.8-p11
1.8-p10
1.8-p9
1.8-p8
1.8-p7
1.8-p6
1.8-p5
1.8-p4
1.8-p3
1.8-p2
1.8-p1
1.8-p0
1.7-p1
1.7-p0
1.6-p8
1.6-p7
1.6-p6
1.6-p5
1.6-p4
1.6-p3
1.6-p2
1.6-p1
1.6-p0
1.5-p6
1.5-p5
1.5-p4
1.5-p3
1.5-p2
1.5-p1
1.5-p0
1.4-p1
1.4-p0
1.3-p5
1.3-p4
1.3-p3
1.3-p2
1.3-p1
1.3-p0
1.2
1.1-p1
1.1
1.0
0.9-p5
0.9-p4
0.9-p3
0.9-p2
0.9-p1
0.9
0.8
0.7
0.6
0.5
0.4
0.3
0.2
0.1
Labels
Clear labels   
bug

   
depends_on_docker

   
enhancement

   
help wanted

   
nice to have

   
waiting for response
No labels
bug
depends_on_docker
enhancement
help wanted
nice to have
waiting for response
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-android#138
No description provided.