[GH-ISSUE #75] (VirtualMachine) Black screen after running the docker butomo1989/docker-android-x86-7.1.1 #59

New issue

Closed

opened 2026-03-01 15:39:46 +03:00 by kerem · 13 comments

kerem commented 2026-03-01 15:39:46 +03:00

Owner

Copy link

Originally created by @GreatBahram on GitHub (Apr 11, 2018).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/75

Operating System:
Ubuntu 16.04.3 LTS

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

Docker Version:
18.02.0-ce

Docker Command to start docker-android:
docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -p 4723:4723 -e DEVICE="Samsung Galaxy S6" --name issue butomo1989/docker-android-x86-7.1.1

Expected Behavior

See a mobile phone at least not just blank screen.

Actual Behavior

Blank screen !

Originally created by @GreatBahram on GitHub (Apr 11, 2018). Original GitHub issue: https://github.com/budtmo/docker-android/issues/75 Operating System: Ubuntu 16.04.3 LTS Docker Image: butomo1989/docker-android-x86-7.1.1 Docker Version: 18.02.0-ce Docker Command to start docker-android: `docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -p 4723:4723 -e DEVICE="Samsung Galaxy S6" --name issue butomo1989/docker-android-x86-7.1.1` ## Expected Behavior See a mobile phone at least not just blank screen. ## Actual Behavior Blank screen ! 

kerem closed this issue 2026-03-01 15:39:46 +03:00

kerem commented 2026-03-01 15:39:47 +03:00

Author

Owner

Copy link

@budtmo commented on GitHub (Apr 11, 2018):

Hi @GreatBahram

Thank you for opening the issue. Could you provide me the full logs?

<!-- gh-comment-id:380387555 --> @budtmo commented on GitHub (Apr 11, 2018): Hi @GreatBahram Thank you for opening the issue. Could you provide me the full logs?

kerem commented 2026-03-01 15:39:47 +03:00

Author

Owner

Copy link

@GreatBahram commented on GitHub (Apr 11, 2018):

docker container logs issue:

2018-04-10 23:42:28,501 CRIT Supervisor running as root (no user in config file)
2018-04-10 23:42:28,503 INFO supervisord started with pid 5
2018-04-10 23:42:29,506 INFO spawned: 'xvfb' with pid 8
2018-04-10 23:42:29,507 INFO spawned: 'port-forward' with pid 9
2018-04-10 23:42:29,509 INFO spawned: 'novnc' with pid 10
2018-04-10 23:42:29,518 INFO spawned: 'openbox' with pid 11
2018-04-10 23:42:29,523 INFO spawned: 'x11vnc' with pid 13
2018-04-10 23:42:29,526 INFO spawned: 'android-screen-mirror' with pid 14
2018-04-10 23:42:29,541 INFO spawned: 'docker-appium' with pid 16
2018-04-10 23:42:29,543 INFO spawned: 'auto-recording' with pid 22
2018-04-10 23:42:29,563 INFO exited: android-screen-mirror (exit status 0; expected)
2018-04-10 23:42:30,618 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-10 23:42:30,618 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-10 23:42:30,618 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-10 23:42:30,618 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-10 23:42:30,618 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-10 23:42:30,618 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-10 23:42:30,619 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-10 23:42:32,453 INFO exited: docker-appium (exit status 1; not expected)
2018-04-10 23:42:35,570 INFO exited: auto-recording (exit status 0; expected)

is this enough ?

<!-- gh-comment-id:380408308 --> @GreatBahram commented on GitHub (Apr 11, 2018): docker container logs issue: ``` 2018-04-10 23:42:28,501 CRIT Supervisor running as root (no user in config file) 2018-04-10 23:42:28,503 INFO supervisord started with pid 5 2018-04-10 23:42:29,506 INFO spawned: 'xvfb' with pid 8 2018-04-10 23:42:29,507 INFO spawned: 'port-forward' with pid 9 2018-04-10 23:42:29,509 INFO spawned: 'novnc' with pid 10 2018-04-10 23:42:29,518 INFO spawned: 'openbox' with pid 11 2018-04-10 23:42:29,523 INFO spawned: 'x11vnc' with pid 13 2018-04-10 23:42:29,526 INFO spawned: 'android-screen-mirror' with pid 14 2018-04-10 23:42:29,541 INFO spawned: 'docker-appium' with pid 16 2018-04-10 23:42:29,543 INFO spawned: 'auto-recording' with pid 22 2018-04-10 23:42:29,563 INFO exited: android-screen-mirror (exit status 0; expected) 2018-04-10 23:42:30,618 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-10 23:42:30,618 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-10 23:42:30,618 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-10 23:42:30,618 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-10 23:42:30,618 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-10 23:42:30,618 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-10 23:42:30,619 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-10 23:42:32,453 INFO exited: docker-appium (exit status 1; not expected) 2018-04-10 23:42:35,570 INFO exited: auto-recording (exit status 0; expected) ``` is this enough ?

kerem commented 2026-03-01 15:39:47 +03:00

Author

Owner

Copy link

@halsn commented on GitHub (Apr 12, 2018):

I have the same question.
Operating System:
Ubuntu 16.04.3 LTS

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

Docker Version:
18.02.0-ce

Docker Command to start docker-android:
docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -p 4723:4723 -e DEVICE="Samsung Galaxy S6" --name android-container butomo1989/docker-android-x86-7.1.1

Here is the log:

2018-04-12 05:32:36,498 CRIT Supervisor running as root (no user in config file)
2018-04-12 05:32:36,511 INFO supervisord started with pid 7
2018-04-12 05:32:37,513 INFO spawned: 'xvfb' with pid 21
2018-04-12 05:32:37,524 INFO spawned: 'port-forward' with pid 22
2018-04-12 05:32:37,544 INFO spawned: 'novnc' with pid 23
2018-04-12 05:32:37,545 INFO spawned: 'openbox' with pid 24
2018-04-12 05:32:37,547 INFO spawned: 'x11vnc' with pid 25
2018-04-12 05:32:37,548 INFO spawned: 'android-screen-mirror' with pid 26
2018-04-12 05:32:37,550 INFO spawned: 'docker-appium' with pid 27
2018-04-12 05:32:37,551 INFO spawned: 'auto-recording' with pid 28
2018-04-12 05:32:37,726 INFO success: android-screen-mirror entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-04-12 05:32:37,727 INFO exited: android-screen-mirror (exit status 0; expected)
2018-04-12 05:32:38,733 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-12 05:32:38,733 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-12 05:32:38,733 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-12 05:32:38,733 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-12 05:32:38,733 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-12 05:32:38,733 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-12 05:32:38,733 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-04-12 05:32:43,765 INFO exited: auto-recording (exit status 0; expected)
2018-04-12 05:35:53,258 INFO exited: docker-appium (exit status 0; expected)

<!-- gh-comment-id:380793938 --> @halsn commented on GitHub (Apr 12, 2018): I have the same question. Operating System: Ubuntu 16.04.3 LTS Docker Image: butomo1989/docker-android-x86-7.1.1 Docker Version: 18.02.0-ce Docker Command to start docker-android: `docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -p 4723:4723 -e DEVICE="Samsung Galaxy S6" --name android-container butomo1989/docker-android-x86-7.1.1` Here is the log: ``` 2018-04-12 05:32:36,498 CRIT Supervisor running as root (no user in config file) 2018-04-12 05:32:36,511 INFO supervisord started with pid 7 2018-04-12 05:32:37,513 INFO spawned: 'xvfb' with pid 21 2018-04-12 05:32:37,524 INFO spawned: 'port-forward' with pid 22 2018-04-12 05:32:37,544 INFO spawned: 'novnc' with pid 23 2018-04-12 05:32:37,545 INFO spawned: 'openbox' with pid 24 2018-04-12 05:32:37,547 INFO spawned: 'x11vnc' with pid 25 2018-04-12 05:32:37,548 INFO spawned: 'android-screen-mirror' with pid 26 2018-04-12 05:32:37,550 INFO spawned: 'docker-appium' with pid 27 2018-04-12 05:32:37,551 INFO spawned: 'auto-recording' with pid 28 2018-04-12 05:32:37,726 INFO success: android-screen-mirror entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2018-04-12 05:32:37,727 INFO exited: android-screen-mirror (exit status 0; expected) 2018-04-12 05:32:38,733 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-12 05:32:38,733 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-12 05:32:38,733 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-12 05:32:38,733 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-12 05:32:38,733 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-12 05:32:38,733 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-12 05:32:38,733 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-12 05:32:43,765 INFO exited: auto-recording (exit status 0; expected) 2018-04-12 05:35:53,258 INFO exited: docker-appium (exit status 0; expected) ```

kerem commented 2026-03-01 15:39:47 +03:00

Author

Owner

Copy link

@budtmo commented on GitHub (Apr 12, 2018):

It works fine on my machine. Do you use normal machine or Virtual machine? have you already activated virtualization on your linux machine? @GreatBahram @halsn

<!-- gh-comment-id:380918029 --> @budtmo commented on GitHub (Apr 12, 2018): It works fine on my machine. Do you use normal machine or Virtual machine? have you already activated virtualization on your linux machine? @GreatBahram @halsn

kerem commented 2026-03-01 15:39:48 +03:00

Author

Owner

Copy link

@halsn commented on GitHub (Apr 13, 2018):

I use a Virtual machine @butomo1989

<!-- gh-comment-id:380993894 --> @halsn commented on GitHub (Apr 13, 2018): I use a Virtual machine @butomo1989

kerem commented 2026-03-01 15:39:48 +03:00

Author

Owner

Copy link

@GreatBahram commented on GitHub (Apr 13, 2018):

I used it on Virtual machine and I'm pretty sure virtualization is on my machine

<!-- gh-comment-id:381045587 --> @GreatBahram commented on GitHub (Apr 13, 2018): I used it on Virtual machine and I'm pretty sure virtualization is on my machine

kerem commented 2026-03-01 15:39:48 +03:00

Author

Owner

Copy link

@budtmo commented on GitHub (Apr 13, 2018):

What kind of VM do you use? and does your VM (not the host) support Virtualization? @GreatBahram @halsn for example Virtualbox doesnt support virtualization but I tried VMware Workstation Player once, and it works.

<!-- gh-comment-id:381082424 --> @budtmo commented on GitHub (Apr 13, 2018): What kind of VM do you use? and does your VM (not the host) support Virtualization? @GreatBahram @halsn for example Virtualbox doesnt support virtualization but I tried VMware Workstation Player once, and it works.

kerem commented 2026-03-01 15:39:48 +03:00

Author

Owner

Copy link

@halsn commented on GitHub (Apr 16, 2018):

I used VMware Workstation 12, but it doesn't work @butomo1989

<!-- gh-comment-id:381465340 --> @halsn commented on GitHub (Apr 16, 2018): I used VMware Workstation 12, but it doesn't work @butomo1989

kerem commented 2026-03-01 15:39:48 +03:00

Author

Owner

Copy link

@GreatBahram commented on GitHub (Apr 16, 2018):

I don't think you're right @butomo1989 since Virtualbox supports Hardware virtualization dude.
Thanks for your explanation

<!-- gh-comment-id:381558559 --> @GreatBahram commented on GitHub (Apr 16, 2018): I don't think you're right @butomo1989 since Virtualbox supports Hardware virtualization dude. Thanks for your explanation

kerem commented 2026-03-01 15:39:48 +03:00

Author

Owner

Copy link

@khalidumarr commented on GitHub (May 6, 2018):

facing same issue using docker native on ubuntu 16.04. @butomo1989, its not only related to VM.

<!-- gh-comment-id:386869741 --> @khalidumarr commented on GitHub (May 6, 2018): facing same issue using docker native on ubuntu 16.04. @butomo1989, its not only related to VM.

kerem commented 2026-03-01 15:39:48 +03:00

Author

Owner

Copy link

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

Hi @khalidumarr ,

it works fine on my machine. Could you give me information about spec of your machine? so I can help you.

<!-- gh-comment-id:388932651 --> @budtmo commented on GitHub (May 14, 2018): Hi @khalidumarr , it works fine on my machine. Could you give me information about spec of your machine? so I can help you.

kerem commented 2026-03-01 15:39:48 +03:00

Author

Owner

Copy link

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

same issue with x86-7.0 and x86-7.1.1 on real HW Intel P6100

EDIT: ok... i need another CPU:

<!-- gh-comment-id:391142344 --> @Adminius commented on GitHub (May 22, 2018): same issue with x86-7.0 and x86-7.1.1 on real HW Intel P6100 EDIT: ok... i need another CPU: 

kerem commented 2026-03-01 15:39:48 +03:00

Author

Owner

Copy link

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

the x86 require KVM and inside the VirtualBox you can not install KVM due to the virtualization of the VM that inhibit the physical virtualization

<!-- gh-comment-id:393097498 --> @pasqualevitale commented on GitHub (May 30, 2018): the x86 require KVM and inside the VirtualBox you can not install KVM due to the virtualization of the VM that inhibit the physical virtualization

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

Subscribe

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#59

No description provided.