search

budtmo / docker-android

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

[🐛 Bug ]: FATAL state #398

Closed atigm closed 6 months ago

atigm commented 6 months ago

Operating System

Ubuntu Server 22.04 LTS

Docker Image

budtmo/docker-android:emulator_12.0

Expected behaviour

Running emulator crashes

Docker Command to start docker-android: docker run --privileged -d -p 10000:4723 -p 10001:5554 -p 10002:5555 -v /mnt/apk:/root/tmp -e DEVICE="Samsung Galaxy S10" -e APPIUM=true --name android budtmo/docker-android:emulator_12.0

I have 

2023-12-07 21:41:20,155 INFO exited: screen-copy (exit status 0; not expected)
2023-12-07 21:41:20,156 INFO gave up: screen-copy entered FATAL state, too many start retries too quickly
2023-12-07 21:41:22,160 INFO spawned: 'docker-appium' with pid 326
2023-12-07 21:41:22,699 INFO exited: docker-appium (exit status 1; not expected)
2023-12-07 21:41:23,701 INFO gave up: docker-appium entered FATAL state, too many start retries too quickly

Actual behaviour

Docker container logs show some processes keep on exiting. The logs are as follows and show that "atd", "screen-copy" and "auto-recording" all enter FATAL state

Logs

docker-android.stderr.log: 

exec(code, run_globals)
  File "/root/src/app.py", line 239, in <module>
    run()
  File "/root/src/app.py", line 218, in run
    prepare_avd(device, avd_name, dp_size)
  File "/root/src/app.py", line 113, in prepare_avd
    subprocess.check_call(creation_cmd, shell=True)
  File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'avdmanager create avd -f -n samsung_galaxy_s10_12.0 -b google_apis/x86_64 -k "system-images;android-31;google_apis;x86_64" -d Samsung\ Galaxy\ S10 -p /opt/android/android_emulator' returned non-zero exit status 1.

docker-android.stdout.log:

Image type: google_apis
[327] [ INFO] app - Device: Samsung Galaxy S10
[327] [ INFO] app - Custom Args: 
[327] [ INFO] app - AVD name: samsung_galaxy_s10_12.0
[327] [ INFO] app - No config file file was found at /root/android_emulator/config.ini. Assuming new device.
[327] [ INFO] app - Preparing emulator...
[327] [ INFO] app - Hardware profile resource path: /root/devices/profiles/samsung_galaxy_s10.xml
[327] [ INFO] app - Hardware profile destination path: /root/.android/devices.xml
[327] [ INFO] app - Command to create avd: avdmanager create avd -f -n samsung_galaxy_s10_12.0 -b google_apis/x86_64 -k "system-images;android-31;google_apis;x86_64" -d Samsung\ Galaxy\ S10 -p /opt/android/android_emulator
atigm commented 6 months ago

On container, I run : avdmanager create avd -f -n samsung_galaxy_s10_12.0 -b google_apis/x86_64 -k "system-images;android-31;google_apis;x86_64" -d Samsung\ Galaxy\ S10 -p /opt/android/android_emulator

I have:

Error: No device found matching --device Samsung Galaxy S10.repository...       
null