You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now im just stuck on docker android picture on noVNC
Logs
WARN[0001] /media/nux/Dataxx/composes/budtomo_android/compose.yaml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 1/1
✔ Container budtomo_android-android-container-1 Created 1.9s
Attaching to android-container-1
android-container-1 | 2024-12-17 02:23:03,140 INFO supervisord started with pid 3
android-container-1 | 2024-12-17 02:23:03,140 INFO supervisord started with pid 4
android-container-1 | 2024-12-17 02:23:03,140 INFO supervisord started with pid 2
android-container-1 | 2024-12-17 02:23:04,145 INFO spawned: 'appium' with pid 8
android-container-1 | 2024-12-17 02:23:04,146 INFO spawned: 'android_port_forward' with pid 9
android-container-1 | 2024-12-17 02:23:04,147 INFO spawned: 'd_screen' with pid 10
android-container-1 | 2024-12-17 02:23:04,152 INFO spawned: 'device' with pid 11
android-container-1 | 2024-12-17 02:23:04,155 INFO spawned: 'd_wm' with pid 12
android-container-1 | 2024-12-17 02:23:04,164 INFO spawned: 'vnc_server' with pid 14
android-container-1 | 2024-12-17 02:23:04,161 INFO spawned: 'log_web_shared' with pid 13
android-container-1 | 2024-12-17 02:23:04,187 INFO spawned: 'vnc_web' with pid 15
android-container-1 | 2024-12-17 02:23:05,144 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,159 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,159 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,172 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,712 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,720 INFO success: appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,720 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,720 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:07,859 INFO exited: device (exit status 1; not expected)
The text was updated successfully, but these errors were encountered:
use sudo docker exec -it <id of docker container> bash
and check logs especially for everything that starts with device_*
use cat for it
and send it here
Operating System
Kali Linux 22.04
Docker Image
docker.io/budtmo/docker-android emulator_11.0
Expected behaviour
Android boot and get menu page
Actual behaviour
Now im just stuck on docker android picture on noVNC
Logs
WARN[0001] /media/nux/Dataxx/composes/budtomo_android/compose.yaml: the attribute
version
is obsolete, it will be ignored, please remove it to avoid potential confusion[+] Running 1/1
✔ Container budtomo_android-android-container-1 Created 1.9s
Attaching to android-container-1
android-container-1 | 2024-12-17 02:23:03,140 INFO supervisord started with pid 3
android-container-1 | 2024-12-17 02:23:03,140 INFO supervisord started with pid 4
android-container-1 | 2024-12-17 02:23:03,140 INFO supervisord started with pid 2
android-container-1 | 2024-12-17 02:23:04,145 INFO spawned: 'appium' with pid 8
android-container-1 | 2024-12-17 02:23:04,146 INFO spawned: 'android_port_forward' with pid 9
android-container-1 | 2024-12-17 02:23:04,147 INFO spawned: 'd_screen' with pid 10
android-container-1 | 2024-12-17 02:23:04,152 INFO spawned: 'device' with pid 11
android-container-1 | 2024-12-17 02:23:04,155 INFO spawned: 'd_wm' with pid 12
android-container-1 | 2024-12-17 02:23:04,164 INFO spawned: 'vnc_server' with pid 14
android-container-1 | 2024-12-17 02:23:04,161 INFO spawned: 'log_web_shared' with pid 13
android-container-1 | 2024-12-17 02:23:04,187 INFO spawned: 'vnc_web' with pid 15
android-container-1 | 2024-12-17 02:23:05,144 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,159 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,159 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,172 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,712 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,720 INFO success: appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,720 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:05,720 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container-1 | 2024-12-17 02:23:07,859 INFO exited: device (exit status 1; not expected)
The text was updated successfully, but these errors were encountered: