budtmo / budtmo/docker-android
[🐛 Bug ]: Cannot work on ubuntu24
- Dominant language
- Python
- Stars
- 15.8k
- Forks
- 1.8k
- Avg merge
- 12h 13m
- Merged PRs (30d)
- 6
Description
### Operating System
ubuntu24
### Docker Image
budtmo/docker-android:emulator_14.0
### Expected behaviour
Can work.My docker compose yml.
```yml
version: "3.8"
services:
android:
image: budtmo/docker-android:emulator_14.0
ports:
- 6081:6080
environment:
- EMULATOR_DEVICE="Samsung Galaxy S10"
- WEB_VNC=true
devices:
- /dev/kvm
```
### Actual behaviour
Only this view.
### Logs
```
2025-02-09 05:28:27,974 INFO supervisord started with pid 9
2025-02-09 05:28:27,984 INFO supervisord started with pid 8
2025-02-09 05:28:27,985 INFO supervisord started with pid 7
2025-02-09 05:28:28,976 INFO spawned: 'appium' with pid 13
2025-02-09 05:28:28,977 INFO spawned: 'device' with pid 14
2025-02-09 05:28:28,979 INFO spawned: 'log_web_shared' with pid 15
2025-02-09 05:28:28,986 INFO spawned: 'android_port_forward' with pid 16
2025-02-09 05:28:28,987 INFO spawned: 'd_screen' with pid 17
2025-02-09 05:28:28,989 INFO spawned: 'd_wm' with pid 18
2025-02-09 05:28:28,991 INFO spawned: 'vnc_server' with pid 19
2025-02-09 05:28:28,992 INFO spawned: 'vnc_web' with pid 20
2025-02-09 05:28:29,197 INFO exited: log_web_shared (exit status 0; not expected)
2025-02-09 05:28:29,217 INFO exited: device (exit status 1; not expected)
2025-02-09 05:28:29,220 INFO gave up: device entered FATAL state, too many start retries too quickly
2025-02-09 05:28:29,220 INFO exited: appium (exit status 0; not expected)
2025-02-09 05:28:29,230 INFO exited: d_wm (exit status 1; not expected)
2025-02-09 05:28:29,273 INFO exited: vnc_server (exit status 1; not expected)
2025-02-09 05:28:30,221 INFO gave up: appium entered FATAL state, too many start retries too quickly
2025-02-09 05:28:30,223 INFO spawned: 'log_web_shared' with pid 52
2025-02-09 05:28:30,234 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-09 05:28:30,277 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-09 05:28:30,278 INFO spawned: 'd_wm' with pid 56
2025-02-09 05:28:30,279 INFO spawned: 'vnc_server' with pid 58
2025-02-09 05:28:30,279 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-09 05:28:30,413 INFO exited: log_web_shared (exit status 0; not expected)
2025-02-09 05:28:31,532 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-09 05:28:31,532 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-09 05:28:32,418 INFO spawned: 'log_web_shared' with pid 75
2025-02-09 05:28:32,597 INFO exited: log_web_shared (exit status 0; not expected)
2025-02-09 05:28:35,601 INFO spawned: 'log_web_shared' with pid 77
2025-02-09 05:28:35,782 INFO exited: log_web_shared (exit status 0; not expected)
2025-02-09 05:28:36,782 INFO gave up: log_web_shared entered FATAL state, too many start retries too quickly
```
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.