port 6080 page has no android UI, just a backgroud

[gituser056391]

Operating System

win10，or synology DSM7.2

Docker Image

budtmo/docker-android:emulator_13.0

Expected behaviour

port 6080 page has no android UI, just a backgroud

Actual behaviour

port 6080 page has no android UI, just a backgroud

Logs

No response

[baipiaoeverything]

I am also facing the same issue.

[khanmenthe]

I am facing maybe facing the same issue, could you run docker exec -it android-container cat device_status after like 30 minutes when it should definitely have started?
For me it says STARTING even after 4 hours, and in the system usage the ram keeps going up, then crashes down, indefinitely, which makes me think it's stuck in a bootloop.

[lheiz]

I had the same issue. In my case not enough disk space was left thus android emulator could not start. For debugging, you can try try to manually start the emulator in a terminal (in the VNC desktop, right click -> Terminal Emulator):

This should give you more information on why the emulator won't start.

[MichaelVasilyev]

I have the similar issue - first boot ok, but no emulator after docker restart.
In my case something wrong with permissions for /dev/kvm inside container

So quick & dirty fix:

#!/bin/sh
docker exec -it -u0 android-container chmod 777 /dev/kvm
docker exec -d android-container /usr/bin/emulator -avd nexus_7_13.0.

[BlueClouDragon]

me too, how to fix this?

[ghmagi]

I had a similar issue.

Manually running the emulator as @lheiz suggests above showed ~ "ERROR: Not enough space to create userdata partition ...".

In my case this may have been because I was running the host Ubuntu in a VirtualBox VM using a dynamically-sized VDI disk. The disk had plenty of space to grow, but didn't. Recreating the Ubuntu host w/ a fixed-size disk seems to have addressed the issue.

[petersmythe]

When restarting a stopped container, I got this error when manually running emulator -avd <device>:

INFO | Warning: could not connect to display :0 ((null):0, (null))
INFO | Info: Could not load the Qt platform plugin "xcb" in "/opt/android/emulator/lib64/qt/plugins" even though it was found. ((null):0, (null))
Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

[pakx]

When restarting a stopped container, I got this error when manually running emulator -avd <device>:

INFO | Warning: could not connect to display :0 ((null):0, (null))
INFO | Info: Could not load the Qt platform plugin "xcb" in "/opt/android/emulator/lib64/qt/plugins" even though it was found. ((null):0, (null))
Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

This should probably be listed as a separate issue, isn't specific to this project, and is something I've come across when using X11 -- what's happening is: when the container if first created it's associated with an X-display; when the container is stopped/re-started and the X-display is not the same (e.g. if re-starting from an RDP session, etc), this error appears. My approach has been to explicitly set a display on docker-run and docker-start.