Operating System

Debian 13

Docker Image

budtmo/docker-android:emulator_14.0

Expected behaviour

COMAND:

docker run -d \
  -p 6080:6080 \
  -e EMULATOR_DEVICE="Samsung Galaxy S10" \
  -e WEB_VNC=true \
  --device /dev/kvm \
  --name android-container \
  budtmo/docker-android:emulator_14.0

EXPECTED BEHAVIOUR:
Android emulator at localhost:6080

FYI:
kvm is enabled and working.

Actual behaviour

STATUS

master@android:~$ docker exec -it android-container cat device_status
STARTING

ISSUE:
Just gets stuck. Left it running over night, still stuck.
WebUI looks like this:

Logs

master@android:~$ docker logs android-container-02
2025-09-11 10:22:28,553 INFO supervisord started with pid 7
2025-09-11 10:22:28,553 INFO supervisord started with pid 8
2025-09-11 10:22:28,554 INFO supervisord started with pid 9
2025-09-11 10:22:29,555 INFO spawned: 'd_screen' with pid 10
2025-09-11 10:22:29,556 INFO spawned: 'android_port_forward' with pid 11
2025-09-11 10:22:29,556 INFO spawned: 'appium' with pid 12
2025-09-11 10:22:29,557 INFO spawned: 'd_wm' with pid 13
2025-09-11 10:22:29,557 INFO spawned: 'device' with pid 14
2025-09-11 10:22:29,559 INFO spawned: 'log_web_shared' with pid 15
2025-09-11 10:22:29,561 INFO spawned: 'vnc_server' with pid 16
2025-09-11 10:22:29,567 INFO spawned: 'vnc_web' with pid 17
2025-09-11 10:22:29,865 WARN exited: log_web_shared (exit status 0; not expected)
2025-09-11 10:22:30,656 INFO success: appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-11 10:22:30,656 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-11 10:22:30,656 INFO exited: appium (exit status 0; expected)
2025-09-11 10:22:30,890 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-11 10:22:30,901 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-11 10:22:30,901 INFO success: d_wm entered RUNNING state, process
has stayed up for > than 1 seconds (startsecs)
2025-09-11 10:22:30,901 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-11 10:22:30,902 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-11 10:22:30,980 INFO spawned: 'log_web_shared' with pid 131
2025-09-11 10:22:31,184 WARN exited: log_web_shared (exit status 0; not expected)
2025-09-11 10:22:32,010 WARN exited: device (exit status 1; not expected)
2025-09-11 10:22:34,014 INFO spawned: 'log_web_shared' with pid 143
2025-09-11 10:22:34,154 WARN exited: log_web_shared (exit status 0; not expected)
2025-09-11 10:22:37,160 INFO spawned: 'log_web_shared' with pid 144
2025-09-11 10:22:37,299 WARN exited: log_web_shared (exit status 0; not expected)
2025-09-11 10:22:38,301 INFO gave up: log_web_shared entered FATAL state,
too many start retries too quickly