Closed hhhaiai closed 1 year ago
i have this too
me too :/
have anyone able to resolve this issue?
I had the same issue when I was using docker-desktop context. After switching to default, it works now. You can check that with the following command:
docker context ls
if default is not in use, type:
docker context use default
It worked for me
Actually I run the container inside a compute engine that doesn't support nested virtualization, after I create new instance with nested virtualization, It works! But I also tried DinD (Docker in Docker) approach, and faced this issue as well (even with the nested virtualization enabled), seems like it require lv 2 nested virtualization to achieve the result I expected.
I have a plan : step 1: If need , install SDK env and emulator tools ; step 2. config cutsom devices and run ; step 3: wait success and some config.
one lib has some commond:(https://github.com/ReactiveCircus/android-emulator-runner) Chinese doc: https://www.yuque.com/sanbo/npozvp/ming-ling-xing-xin-jian-mo-ni-qi-androidemulatorru
please check the virtualization configuration. I will close the issue for now, but feel free to reopen it
offline🐛 Bug Report
Operating System:
Ubuntu 20.04
platform
github action. newest docker.
LOG