[GH-ISSUE #178] Can't see the GUI inside the container docker-android-x86-8.1 #129

New issue

Closed

opened 2026-03-01 15:40:45 +03:00 by kerem · 3 comments

kerem commented

2026-03-01 15:40:45 +03:00

Owner

Originally created by @reardenlife on GitHub (Jul 18, 2019).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/178

Tried to run the following on Cent OS 7 with docker-ce:

 [root opt]# docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" --name android-container budtmo/docker-android-x86-8.1

But all I see in the browser is this:

Docker logs:

 [root opt]# docker logs ebd54b928f33
 2019-07-17 21:57:33,986 CRIT Supervisor running as root (no user in config file)
 2019-07-17 21:57:34,030 INFO supervisord started with pid 6
 2019-07-17 21:57:35,048 INFO spawned: 'xvfb' with pid 9
 2019-07-17 21:57:35,116 INFO spawned: 'port-forward' with pid 14
 2019-07-17 21:57:35,309 INFO spawned: 'novnc' with pid 16
 2019-07-17 21:57:35,459 INFO spawned: 'openbox' with pid 17
 2019-07-17 21:57:35,565 INFO spawned: 'x11vnc' with pid 18
 2019-07-17 21:57:35,733 INFO spawned: 'android-screen-mirror' with pid 19
 2019-07-17 21:57:35,867 INFO spawned: 'docker-appium' with pid 25
 2019-07-17 21:57:36,180 INFO spawned: 'atd' with pid 30
 2019-07-17 21:57:36,389 INFO spawned: 'auto-recording' with pid 34
 2019-07-17 21:57:36,664 INFO spawned: 'adb-utils' with pid 37
 2019-07-17 21:57:36,801 INFO exited: android-screen-mirror (exit status 0; expected)
 2019-07-17 21:57:36,937 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
 2019-07-17 21:57:36,938 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
 2019-07-17 21:57:36,939 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
 2019-07-17 21:57:36,939 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
 2019-07-17 21:57:36,940 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
 2019-07-17 21:57:36,940 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
 2019-07-17 21:57:37,019 INFO success: atd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:37,058 INFO exited: atd (exit status 0; expected)
 2019-07-17 21:57:37,384 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
 2019-07-17 21:57:37,611 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
 2019-07-17 21:57:43,439 INFO exited: auto-recording (exit status 0; expected)
 2019-07-17 21:59:15,061 INFO exited: docker-appium (exit status 0; expected)

Any idea what might be wrong?

Originally created by @reardenlife on GitHub (Jul 18, 2019). Original GitHub issue: https://github.com/budtmo/docker-android/issues/178 Tried to run the following on Cent OS 7 with docker-ce: ```bash [root opt]# docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" --name android-container budtmo/docker-android-x86-8.1 ``` But all I see in the browser is this: ![Screenshot_20190718_081407](https://user-images.githubusercontent.com/45923995/61460827-29bb1c80-a935-11e9-8197-2b15322642eb.png) Docker logs: ```text [root opt]# docker logs ebd54b928f33 2019-07-17 21:57:33,986 CRIT Supervisor running as root (no user in config file) 2019-07-17 21:57:34,030 INFO supervisord started with pid 6 2019-07-17 21:57:35,048 INFO spawned: 'xvfb' with pid 9 2019-07-17 21:57:35,116 INFO spawned: 'port-forward' with pid 14 2019-07-17 21:57:35,309 INFO spawned: 'novnc' with pid 16 2019-07-17 21:57:35,459 INFO spawned: 'openbox' with pid 17 2019-07-17 21:57:35,565 INFO spawned: 'x11vnc' with pid 18 2019-07-17 21:57:35,733 INFO spawned: 'android-screen-mirror' with pid 19 2019-07-17 21:57:35,867 INFO spawned: 'docker-appium' with pid 25 2019-07-17 21:57:36,180 INFO spawned: 'atd' with pid 30 2019-07-17 21:57:36,389 INFO spawned: 'auto-recording' with pid 34 2019-07-17 21:57:36,664 INFO spawned: 'adb-utils' with pid 37 2019-07-17 21:57:36,801 INFO exited: android-screen-mirror (exit status 0; expected) 2019-07-17 21:57:36,937 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:36,938 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:36,939 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:36,939 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:36,940 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:36,940 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:37,019 INFO success: atd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:37,058 INFO exited: atd (exit status 0; expected) 2019-07-17 21:57:37,384 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:37,611 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-07-17 21:57:43,439 INFO exited: auto-recording (exit status 0; expected) 2019-07-17 21:59:15,061 INFO exited: docker-appium (exit status 0; expected) ``` Any idea what might be wrong?

kerem closed this issue

2026-03-01 15:40:45 +03:00

kerem commented

2026-03-01 15:40:46 +03:00

Author

Owner

@reardenlife commented on GitHub (Jul 22, 2019):

I wonder if this is somehow connected to absence of Nested Virtualization on my KVM machine.
Or ... if it is connected to insufficiency of RAM.
I just tried to run Android x86 8.1 within qemu over VNC. And I've got a black screen on the system startup, which is somewhat similar to what I am experiencing here.

@reardenlife commented on GitHub (Jul 22, 2019): I wonder if this is somehow connected to absence of Nested Virtualization on my KVM machine. Or ... if it is connected to insufficiency of RAM. I just tried to run Android x86 8.1 within qemu over VNC. And I've got a black screen on the system startup, which is somewhat similar to what I am experiencing here.

kerem commented

2026-03-01 15:40:46 +03:00

Author

Owner

@RuslanSelenium commented on GitHub (Jul 24, 2019):

The same problem

@RuslanSelenium commented on GitHub (Jul 24, 2019): The same problem

kerem commented

2026-03-01 15:40:46 +03:00

Author

Owner

@budtmo commented on GitHub (Jul 25, 2019):