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

[GH-ISSUE #69] Black screen after running the docker (arm image) #56

New issue
Closed
opened 2026-03-01 15:39:44 +03:00 by kerem · 17 comments
kerem commented 2026-03-01 15:39:44 +03:00
Owner
Copy link

Originally created by @moradkh on GitHub (Feb 26, 2018).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/69

Please make sure that it is an issue / a feature request. If it is a question / help wanted, please visit our group chat. Thank you!

Operating System: Mac Sierra 10.12.6

Docker Image: butomo1989/docker-android-arm-7.1.1

Docker Version: 1.19.0

Docker Command to start docker-android:

docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Nexus s" -e APPIUM=True --name android-container butomo1989/docker-android-arm-7.1.1

Expected Behavior

When i run the docker and then I go the the 127.0.0.1:6080 in my local machine, I get black screen,
also when I run adb devices inside the docker container, I get nothing

OSXICGIT072:~ mk90106$ docker run -it butomo1989/docker-android-arm-7.1.1 bash
root@5c65fde9a15b:~# adb devices
List of devices attach
screen shot 2018-02-26 at 3 40 02 pm
ed

root@5c65fde9a15b:~#

Actual Behavior

  1. Need to find the device in the docker image.
  2. Need to see the UI of the screen using the noVnc in my hosted localhost.

Any suggestions ?

Originally created by @moradkh on GitHub (Feb 26, 2018). Original GitHub issue: https://github.com/budtmo/docker-android/issues/69 **Please make sure that it is an issue / a feature request. If it is a question / help wanted, please visit [our group chat](https://gitter.im/butomo1989/docker-android). Thank you!** Operating System: Mac Sierra 10.12.6 Docker Image: butomo1989/docker-android-arm-7.1.1 Docker Version: 1.19.0 Docker Command to start docker-android: <!-- docker run ... --> docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Nexus s" -e APPIUM=True --name android-container butomo1989/docker-android-arm-7.1.1 ## Expected Behavior When i run the docker and then I go the the 127.0.0.1:6080 in my local machine, I get black screen, also when I run adb devices inside the docker container, I get nothing > OSXICGIT072:~ mk90106$ docker run -it butomo1989/docker-android-arm-7.1.1 bash > root@5c65fde9a15b:~# adb devices > List of devices attach ![screen shot 2018-02-26 at 3 40 02 pm](https://user-images.githubusercontent.com/1182988/36673455-8773f1b2-1b0b-11e8-8362-6fd32c1efaad.png) ed > > root@5c65fde9a15b:~# ## Actual Behavior 1. Need to find the device in the docker image. 2. Need to see the UI of the screen using the noVnc in my hosted localhost. Any suggestions ?
kerem 2026-03-01 15:39:44 +03:00
kerem commented 2026-03-01 15:39:45 +03:00
Author
Owner
Copy link

@nam-edi commented on GitHub (Feb 26, 2018):

Hi,

I have the same problem...

Logs:

2018-02-26 08:18:15,932 CRIT Supervisor running as root (no user in config file)
2018-02-26 08:18:15,936 INFO supervisord started with pid 5
2018-02-26 08:18:16,940 INFO spawned: 'xvfb' with pid 8
2018-02-26 08:18:16,942 INFO spawned: 'port-forward' with pid 9
2018-02-26 08:18:16,945 INFO spawned: 'novnc' with pid 10
2018-02-26 08:18:16,947 INFO spawned: 'openbox' with pid 11
2018-02-26 08:18:16,949 INFO spawned: 'x11vnc' with pid 12
2018-02-26 08:18:16,950 INFO spawned: 'android-screen-mirror' with pid 13
2018-02-26 08:18:16,952 INFO spawned: 'docker-appium' with pid 14
2018-02-26 08:18:16,954 INFO spawned: 'auto-recording' with pid 15
2018-02-26 08:18:16,979 INFO success: android-screen-mirror entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-26 08:18:16,985 INFO exited: android-screen-mirror (exit status 0; expected)
2018-02-26 08:18:18,051 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-02-26 08:18:18,051 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-02-26 08:18:18,051 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-02-26 08:18:18,051 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-02-26 08:18:18,051 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-02-26 08:18:18,051 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-02-26 08:18:18,051 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-02-26 08:18:23,012 INFO exited: auto-recording (exit status 0; expected)

<!-- gh-comment-id:368560927 --> @nam-edi commented on GitHub (Feb 26, 2018): Hi, I have the same problem... Logs: > 2018-02-26 08:18:15,932 CRIT Supervisor running as root (no user in config file) > 2018-02-26 08:18:15,936 INFO supervisord started with pid 5 > 2018-02-26 08:18:16,940 INFO spawned: 'xvfb' with pid 8 > 2018-02-26 08:18:16,942 INFO spawned: 'port-forward' with pid 9 > 2018-02-26 08:18:16,945 INFO spawned: 'novnc' with pid 10 > 2018-02-26 08:18:16,947 INFO spawned: 'openbox' with pid 11 > 2018-02-26 08:18:16,949 INFO spawned: 'x11vnc' with pid 12 > 2018-02-26 08:18:16,950 INFO spawned: 'android-screen-mirror' with pid 13 > 2018-02-26 08:18:16,952 INFO spawned: 'docker-appium' with pid 14 > 2018-02-26 08:18:16,954 INFO spawned: 'auto-recording' with pid 15 > 2018-02-26 08:18:16,979 INFO success: android-screen-mirror entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) > 2018-02-26 08:18:16,985 INFO exited: android-screen-mirror (exit status 0; expected) > 2018-02-26 08:18:18,051 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) > 2018-02-26 08:18:18,051 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) > 2018-02-26 08:18:18,051 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) > 2018-02-26 08:18:18,051 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) > 2018-02-26 08:18:18,051 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) > 2018-02-26 08:18:18,051 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) > 2018-02-26 08:18:18,051 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) > 2018-02-26 08:18:23,012 INFO exited: auto-recording (exit status 0; expected)
kerem commented 2026-03-01 15:39:45 +03:00
Author
Owner
Copy link

@mmineo-ds commented on GitHub (Feb 26, 2018):

Me too, using a Mac High Sierra (latest version)
I ran
➜ ~ docker exec -it android-container tail -f /var/log/supervisor/docker-android.stdout.log

And I got this log:

System image: armeabi-v7a
Image type: google_apis
[28] [ INFO] app - Device: Nexus 5
[28] [ INFO] app - AVD name: nexus_5_7.1.1
[28] [ INFO] app - Preparing emulator...
[28] [ INFO] app - Command to create avd: avdmanager create avd -f -n nexus_5_7.1.1 -b google_apis/armeabi-v7a -k "system-images;android-25;google_apis;armeabi-v7a" -d Nexus\ 5 -p /root/android_emulator
[28] [ INFO] app - Skin was added in config.ini
[28] [ INFO] app - Run emulator...
[28] [ INFO] app - Run appium server...
[28] [ INFO] app - Connect to selenium grid? False
emulator: warning: opening audio output failed

Your emulator is out of date, please update by launching Android Studio:
 - Start Android Studio
 - Select menu "Tools > Android > SDK Manager"
 - Click "SDK Tools" tab
 - Check "Android Emulator" checkbox
 - Click "OK"
<!-- gh-comment-id:368563088 --> @mmineo-ds commented on GitHub (Feb 26, 2018): Me too, using a Mac High Sierra (latest version) I ran ➜ ~ docker exec -it android-container tail -f /var/log/supervisor/docker-android.stdout.log And I got this log: ``` System image: armeabi-v7a Image type: google_apis [28] [ INFO] app - Device: Nexus 5 [28] [ INFO] app - AVD name: nexus_5_7.1.1 [28] [ INFO] app - Preparing emulator... [28] [ INFO] app - Command to create avd: avdmanager create avd -f -n nexus_5_7.1.1 -b google_apis/armeabi-v7a -k "system-images;android-25;google_apis;armeabi-v7a" -d Nexus\ 5 -p /root/android_emulator [28] [ INFO] app - Skin was added in config.ini [28] [ INFO] app - Run emulator... [28] [ INFO] app - Run appium server... [28] [ INFO] app - Connect to selenium grid? False emulator: warning: opening audio output failed Your emulator is out of date, please update by launching Android Studio: - Start Android Studio - Select menu "Tools > Android > SDK Manager" - Click "SDK Tools" tab - Check "Android Emulator" checkbox - Click "OK" ```
kerem commented 2026-03-01 15:39:45 +03:00
Author
Owner
Copy link

@dorangao commented on GitHub (Feb 28, 2018):

+1, using a Mac High Sierra (latest version)
Same behaviors for all different versions (arm) tried.

<!-- gh-comment-id:369364366 --> @dorangao commented on GitHub (Feb 28, 2018): +1, using a Mac High Sierra (latest version) Same behaviors for all different versions (arm) tried.
kerem commented 2026-03-01 15:39:45 +03:00
Author
Owner
Copy link

@thelittlefireman commented on GitHub (Mar 5, 2018):

Same issue for me but on Synology server (unix base and no KVM)

<!-- gh-comment-id:370415913 --> @thelittlefireman commented on GitHub (Mar 5, 2018): Same issue for me but on Synology server (unix base and no KVM)
kerem commented 2026-03-01 15:39:45 +03:00
Author
Owner
Copy link

@richardpenman commented on GitHub (Mar 7, 2018):

Same for me on Mac Sierra 10.12.6 - all arm versions I tried have blank screen.

<!-- gh-comment-id:371286203 --> @richardpenman commented on GitHub (Mar 7, 2018): Same for me on Mac Sierra 10.12.6 - all arm versions I tried have blank screen.
kerem commented 2026-03-01 15:39:45 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Mar 8, 2018):

I think the issue comes from the emulator. We will try to update the emulator version. please consider to use x86 image. If you are using windows or OSX, you can run it under VMWare. It is faster than arm image and besides I won't support arm image in the future because of the its performance.

<!-- gh-comment-id:371443485 --> @budtmo commented on GitHub (Mar 8, 2018): I think the issue comes from the emulator. We will try to update the emulator version. please consider to use x86 image. If you are using windows or OSX, you can run it under VMWare. It is faster than arm image and besides I won't support arm image in the future because of the its performance.
kerem commented 2026-03-01 15:39:45 +03:00
Author
Owner
Copy link

@greenerchen commented on GitHub (Mar 8, 2018):

I have a workaround. You may exit the emulator first. Open a terminal emulator and start an emulator again using command line.

$ emulator -avd <emulator_name> -gpu off -noaudio

Use the avd name existed in your /root/.android/avd.
Then wake up the emulator by clicking the power button on the panel.

<!-- gh-comment-id:371525062 --> @greenerchen commented on GitHub (Mar 8, 2018): I have a workaround. You may exit the emulator first. Open a terminal emulator and start an emulator again using command line. ``` $ emulator -avd <emulator_name> -gpu off -noaudio ``` Use the avd name existed in your /root/.android/avd. Then wake up the emulator by clicking the power button on the panel.
kerem commented 2026-03-01 15:39:45 +03:00
Author
Owner
Copy link

@s417-lama commented on GitHub (Mar 23, 2018):

I had the same issue on Ubuntu 16.04.
In the case of me, this is because I started the emulator with VirtualBox running. The emulator cannot start with VirtualBox or VMWare running, so I had to shutdown VirtualBox.

<!-- gh-comment-id:375574719 --> @s417-lama commented on GitHub (Mar 23, 2018): I had the same issue on Ubuntu 16.04. In the case of me, this is because I started the emulator with VirtualBox running. The emulator cannot start with VirtualBox or VMWare running, so I had to shutdown VirtualBox.
kerem commented 2026-03-01 15:39:46 +03:00
Author
Owner
Copy link

@Kignuf commented on GitHub (Mar 27, 2018):

I'm experiencing the same issue.
MacOSX 10.13.3
Docker 18.03.0-ce, build 0520e24

Logcat logs (see timestamps to grasp how slow it is)
https://gist.github.com/Kignuf/28b12ad490e243fbd18e186d2c17c909

<!-- gh-comment-id:376459893 --> @Kignuf commented on GitHub (Mar 27, 2018): I'm experiencing the same issue. MacOSX 10.13.3 Docker 18.03.0-ce, build 0520e24 Logcat logs (see timestamps to grasp how slow it is) https://gist.github.com/Kignuf/28b12ad490e243fbd18e186d2c17c909
kerem commented 2026-03-01 15:39:46 +03:00
Author
Owner
Copy link

@AndreSand commented on GitHub (Apr 4, 2018):

I also have the same issue :(
MacOSX 10.13.1

<!-- gh-comment-id:378697931 --> @AndreSand commented on GitHub (Apr 4, 2018): I also have the same issue :( MacOSX 10.13.1
kerem commented 2026-03-01 15:39:46 +03:00
Author
Owner
Copy link

@Shinoby1992 commented on GitHub (Apr 10, 2018):

i have this issue running on a ubuntu 16 vm
its get unhealthy and black screen when i connect to the vnc
and the docker compose file does not work the template, i have to create it custom single

<!-- gh-comment-id:380276969 --> @Shinoby1992 commented on GitHub (Apr 10, 2018): i have this issue running on a ubuntu 16 vm its get unhealthy and black screen when i connect to the vnc and the docker compose file does not work the template, i have to create it custom single
kerem commented 2026-03-01 15:39:46 +03:00
Author
Owner
Copy link

@Nedervino commented on GitHub (May 14, 2018):

+1, using MacOSX High Sierra (10.13.4) and with the exact same logs as CapDam. @butomo1989 any update on a possible fix that doesn't require a hypervisor?

<!-- gh-comment-id:388757949 --> @Nedervino commented on GitHub (May 14, 2018): +1, using MacOSX High Sierra (10.13.4) and with the exact same logs as CapDam. @butomo1989 any update on a possible fix that doesn't require a hypervisor?
kerem commented 2026-03-01 15:39:46 +03:00
Author
Owner
Copy link

@moradkh commented on GitHub (May 22, 2018):

any update ? I can help with this

<!-- gh-comment-id:390967017 --> @moradkh commented on GitHub (May 22, 2018): any update ? I can help with this
kerem commented 2026-03-01 15:39:46 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (May 22, 2018):

Hi @Nedervino @moradkh ,

Please use VMWare to run x86 image, because the performance of arm image is really slow and cause a lot of issues so it would be great if you can investigate it and create PR.

<!-- gh-comment-id:391054480 --> @budtmo commented on GitHub (May 22, 2018): Hi @Nedervino @moradkh , Please use VMWare to run x86 image, because the performance of arm image is really slow and cause a lot of issues so it would be great if you can investigate it and create PR.
kerem commented 2026-03-01 15:39:46 +03:00
Author
Owner
Copy link

@pasqualevitale commented on GitHub (May 31, 2018):

VMWare (as all hypervisor) are not able to run KVM, and x86 requires KVM, so you have to use a working image of emulator with arm for VMs

<!-- gh-comment-id:393585626 --> @pasqualevitale commented on GitHub (May 31, 2018): VMWare (as all hypervisor) are not able to run KVM, and x86 requires KVM, so you have to use a working image of emulator with arm for VMs
kerem commented 2026-03-01 15:39:46 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (May 31, 2018):

For windows you can try VMWare player. I tried it last time and it works. for Mac please take a look in readme how it works, somebody contributed to the documentation last time.

<!-- gh-comment-id:393589372 --> @budtmo commented on GitHub (May 31, 2018): For windows you can try VMWare player. I tried it last time and it works. for Mac please take a look in readme how it works, somebody contributed to the documentation last time.
kerem commented 2026-03-01 15:39:46 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Jul 5, 2018):

I will close this issue, because I will not support arm image in the future. Please use VM that support virtualization to be able to run x86 image.

<!-- gh-comment-id:402731371 --> @budtmo commented on GitHub (Jul 5, 2018): I will close this issue, because I will not support arm image in the future. Please use VM that support virtualization to be able to run x86 image.
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#56
No description provided.