budtmo / budtmo/docker-android

[🐛 Bug ]: Cannot work on windows 11

Open
#488 4 comments 3 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
15.8k
Forks
1.8k
Avg merge
12h 13m
Merged PRs (30d)
6

Description

### Operating System

Windows 11

### Docker Image

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

Showing emulator

### Actual behaviour

Only view

![Image](https://github.com/user-attachments/assets/a638d17c-0169-4749-a77c-a3c322ebb888)

### Logs

2025-02-12 10:44:19 2025-02-12 03:44:19,807 INFO supervisord started with pid 7
2025-02-12 10:44:19 2025-02-12 03:44:19,807 INFO supervisord started with pid 8
2025-02-12 10:44:19 2025-02-12 03:44:19,812 INFO supervisord started with pid 9
2025-02-12 10:44:20 2025-02-12 03:44:20,810 INFO spawned: 'android_port_forward' with pid 13
2025-02-12 10:44:20 2025-02-12 03:44:20,810 INFO spawned: 'd_screen' with pid 14
2025-02-12 10:44:20 2025-02-12 03:44:20,813 INFO spawned: 'd_wm' with pid 15
2025-02-12 10:44:20 2025-02-12 03:44:20,816 INFO spawned: 'appium' with pid 16
2025-02-12 10:44:20 2025-02-12 03:44:20,816 INFO spawned: 'vnc_server' with pid 17
2025-02-12 10:44:20 2025-02-12 03:44:20,822 INFO spawned: 'device' with pid 18
2025-02-12 10:44:20 2025-02-12 03:44:20,824 INFO spawned: 'vnc_web' with pid 19
2025-02-12 10:44:20 2025-02-12 03:44:20,840 INFO spawned: 'log_web_shared' with pid 20
2025-02-12 10:44:21 2025-02-12 03:44:21,690 INFO exited: appium (exit status 0; not expected)
2025-02-12 10:44:21 2025-02-12 03:44:21,758 INFO gave up: appium entered FATAL state, too many start retries too quickly
2025-02-12 10:44:21 2025-02-12 03:44:21,758 INFO exited: log_web_shared (exit status 0; not expected)
2025-02-12 10:44:21 2025-02-12 03:44:21,873 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-12 10:44:21 2025-02-12 03:44:21,873 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-12 10:44:21 2025-02-12 03:44:21,874 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-12 10:44:21 2025-02-12 03:44:21,874 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-12 10:44:22 2025-02-12 03:44:22,614 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-12 10:44:22 2025-02-12 03:44:22,760 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-12 10:44:22 2025-02-12 03:44:22,761 INFO spawned: 'log_web_shared' with pid 65
2025-02-12 10:44:23 2025-02-12 03:44:23,177 INFO exited: log_web_shared (exit status 0; not expected)
2025-02-12 10:44:25 2025-02-12 03:44:25,304 INFO spawned: 'log_web_shared' with pid 121
2025-02-12 10:44:26 2025-02-12 03:44:26,093 INFO exited: log_web_shared (exit status 0; not expected)
2025-02-12 10:44:29 2025-02-12 03:44:29,110 INFO spawned: 'log_web_shared' with pid 198
2025-02-12 10:44:29 2025-02-12 03:44:29,556 INFO exited: log_web_shared (exit status 0; not expected)
2025-02-12 10:44:29 2025-02-12 03:44:29,578 INFO gave up: log_web_shared entered FATAL state, too many start retries too quickly
2025-02-12 10:48:56 2025-02-12 03:47:22,325 INFO exited: device (exit status 1; not expected)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.