budtmo / budtmo/docker-android

Low performance on nested virtualization environment

Open
#341 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
15.8k
Forks
1.8k
Avg merge
12h 13m
Merged PRs (30d)
6

Description

Hello! My team is trying to emulate virtual devices using Android Kubernetes Services. We are able to send Selenium tests, but it takes up to 20 minutes to boot depending on the docker image. 7.1.1 is fast enough but the Chrome and Chromedriver versions are a little old and we are receiving some issues because of that. We are using a device with nested-virtualization enabled. Our machine is Standard_F4s_v2 (8 RAM, 4 CPU cores, no GPU), which has enough RAM and CPU to run the device.

We tried environment variables like -gpu off -noboot-animation, but it just made the device disappear or did nothing.

Example of a part of an AKS YAML file:

```
- name: EMULATOR_ARGS
value: '-gpu off'
- name: LD_LIBRARY_PATH
value: >-
/root/emulator/lib64/qt/lib/:/root/emulator/lib64/:/root/emulator/lib64/gles_swiftshader/
```

Is there a way to solve that? Any suggestions on what should we do instead to run virtual devices? Thank you!

Let me know is more information is needed.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.