search

budtmo / docker-android

Android in docker solution with noVNC supported and video recording
Other
9.61k stars 1.27k forks source link

[🐛 Bug ]: Mount Failed and Can't inrease storage #450

Open Chr0nixz opened 2 months ago

Chr0nixz commented 2 months ago

Operating System

Ubuntu 24.04

Docker Image

budtmo/docker-android:emulator_11.0

Expected behaviour

My start command: docker run -v data:/home/androidusr -v root:/root -d --privileged -p 5554:5554 -p 5555:5555 -p 6080:6080 -e EMULATOR_DEVICE="Samsung Galaxy S10" -e WEB_VNC=true -e EMULATOR_MEMORY=8192m -e EMULATOR_DATA_PARTITION=16384m --device /dev/kvm --name android-container budtmo/docker-android:emulator_11.0 The container files should be saved to /home/androidusr and /root and the emulator's storage should be 16G

Actual behaviour

/home/androidusr and /root are empty(Data persisting failed) The storage of the emulator is still 8G(default)

Logs

2024-07-18 06:13:22,814 INFO supervisord started with pid 7 2024-07-18 06:13:22,830 INFO supervisord started with pid 8 2024-07-18 06:13:22,833 INFO supervisord started with pid 9 2024-07-18 06:13:23,817 INFO spawned: 'd_screen' with pid 13 2024-07-18 06:13:23,821 INFO spawned: 'd_wm' with pid 14 2024-07-18 06:13:23,823 INFO spawned: 'vnc_server' with pid 15 2024-07-18 06:13:23,824 INFO spawned: 'vnc_web' with pid 16 2024-07-18 06:13:23,832 INFO spawned: 'android_port_forward' with pid 17 2024-07-18 06:13:23,836 INFO spawned: 'appium' with pid 18 2024-07-18 06:13:23,840 INFO spawned: 'device' with pid 19 2024-07-18 06:13:23,843 INFO spawned: 'log_web_shared' with pid 20 2024-07-18 06:13:24,042 INFO exited: d_wm (exit status 1; not expected) 2024-07-18 06:13:24,043 INFO exited: vnc_server (exit status 1; not expected) 2024-07-18 06:13:24,054 INFO exited: appium (exit status 0; not expected) 2024-07-18 06:13:24,054 INFO gave up: appium entered FATAL state, too many start retries too quickly 2024-07-18 06:13:24,055 INFO exited: log_web_shared (exit status 0; not expected) 2024-07-18 06:13:25,015 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-07-18 06:13:25,015 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-07-18 06:13:25,032 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-07-18 06:13:25,056 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-07-18 06:13:25,057 INFO spawned: 'log_web_shared' with pid 56 2024-07-18 06:13:25,235 INFO exited: log_web_shared (exit status 0; not expected) 2024-07-18 06:13:26,021 INFO spawned: 'd_wm' with pid 58 2024-07-18 06:13:26,022 INFO spawned: 'vnc_server' with pid 59 2024-07-18 06:13:27,239 INFO spawned: 'log_web_shared' with pid 77 2024-07-18 06:13:27,327 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-07-18 06:13:27,327 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-07-18 06:13:27,446 INFO exited: log_web_shared (exit status 0; not expected) 2024-07-18 06:13:30,452 INFO spawned: 'log_web_shared' with pid 91 2024-07-18 06:13:30,672 INFO exited: log_web_shared (exit status 0; not expected) 2024-07-18 06:13:31,674 INFO gave up: log_web_shared entered FATAL state, too many start retries too quickly

Cloud-121 commented 2 months ago

Same issues here.