(VirtualMachine) Black screen after running the docker butomo1989/docker-android-x86-7.1.1

[GreatBahram]

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 !

[budtmo]

Hi @GreatBahram

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

[GreatBahram]

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 ?

[halsn]

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)

[budtmo]

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

[halsn]

I use a Virtual machine @butomo1989

[GreatBahram]

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

[budtmo]

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.

[halsn]

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

[GreatBahram]

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

[khalidumarr]

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

[budtmo]

Hi @khalidumarr ,

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

[Adminius]

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

EDIT: ok... i need another CPU:

[pasqualevitale]

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