New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug ]: Windows 11 -> VMware -> Ubuntu 22 -> Docker -> BOOTING #405
Comments
same :( |
same here with a dedicated Ubuntu server 22.04 |
root@server:/home/demon# docker logs -f b8f3f9c977f7 --tail 1000 |
ohhh I found a post here with the same issue, it seems disk space: |
this was the solution with image budtmo/docker-android:emulator_11.0 |
yeah i even get on the other images the same error. cant start the emu. is somebody able to ? then i know at least that its my personal issue :D |
is this project dead ? :( |
I also encountered this problem. |
I also, but is ubuntu 24.04 |
enter the vnc and open the terminal,if everying is ok that the emulator will be worked,but will display u error; |
Operating System
Ubuntu 22.04
Docker Image
budtmo/docker-android:emulator_11.0
Expected behaviour
-> docker ps
-> device_status
-> kvm
When I open http://192.168.0.62:6080/
it successfully connecting to VNC but not showing the device as expected.
I executed
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_11.0
Actual behaviour
It's hanging on BOOTING state and http://192.168.0.62:6080/ address not showing the device.
Logs
root@ubuntu:/home/sa# docker logs -f 9e --tail 1000
2024-01-27 07:47:58,265 INFO supervisord started with pid 8
2024-01-27 07:47:58,265 INFO supervisord started with pid 9
2024-01-27 07:47:58,266 INFO supervisord started with pid 7
2024-01-27 07:47:59,270 INFO spawned: 'android_port_forward' with pid 13
2024-01-27 07:47:59,270 INFO spawned: 'd_screen' with pid 15
2024-01-27 07:47:59,270 INFO spawned: 'appium' with pid 14
2024-01-27 07:47:59,273 INFO spawned: 'device' with pid 16
2024-01-27 07:47:59,273 INFO spawned: 'd_wm' with pid 17
2024-01-27 07:47:59,275 INFO spawned: 'log_web_shared' with pid 18
2024-01-27 07:47:59,285 INFO spawned: 'vnc_server' with pid 19
2024-01-27 07:47:59,286 INFO spawned: 'vnc_web' with pid 20
2024-01-27 07:47:59,434 INFO exited: log_web_shared (exit status 0; not expected)
2024-01-27 07:47:59,435 INFO exited: appium (exit status 0; not expected)
2024-01-27 07:48:00,417 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-27 07:48:00,431 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-27 07:48:00,431 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-27 07:48:00,432 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-27 07:48:00,432 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-27 07:48:00,436 INFO gave up: appium entered FATAL state, too many start retries too quickly
2024-01-27 07:48:00,436 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-27 07:48:00,436 INFO spawned: 'log_web_shared' with pid 65
2024-01-27 07:48:00,583 INFO exited: log_web_shared (exit status 0; not expected)
2024-01-27 07:48:03,574 INFO spawned: 'log_web_shared' with pid 158
2024-01-27 07:48:03,720 INFO exited: log_web_shared (exit status 0; not expected)
2024-01-27 07:48:06,727 INFO spawned: 'log_web_shared' with pid 160
2024-01-27 07:48:06,882 INFO exited: log_web_shared (exit status 0; not expected)
2024-01-27 07:48:07,883 INFO gave up: log_web_shared entered FATAL state, too many start retries too quickly
The text was updated successfully, but these errors were encountered: