Giters

amrsa1 / Android-Emulator-image

The use of this Docker image simplifies the process of running an Android emulator within a Docker container

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

emulators not found

moknit opened this issue · comments

commented

~/Android-Emulator-image$ sudo docker exec --privileged -it -e EMULATOR_TIMEOUT=300 androidContainer bash -c "./start_emu_headless.sh"

  • daemon not running; starting now at tcp:5037
  • daemon started successfully
    linux-gnu: emulator @nexus -no-window -no-snapshot -noaudio -no-boot-anim -memory 2048 -accel off -camera-back none -gpu off
    nohup: appending output to 'nohup.out'
    ==> Checking emulator booting up status 🧐
    ==> adb: no devices/emulators found, please wait ⠇
commented

Same problem

commented

What device you are using guys ?

commented

Nexus. Just running command by command as described in README file. At leas in my case I'm running on Ubuntu 22.04 Docker host.

Running emulator @nexus -no-window -no-snapshot -noaudio -no-boot-anim -memory 2048 -accel off -camera-back none -verbose from within the container just ends up hanging like this:
image

On the right side in the screenshot you can see that ADB inside the container is not seeing emulator at all.

commented

I get the same result even if I run it locally on my Apple M2

commented

~/Android-Emulator-image$ sudo docker exec --privileged -it -e EMULATOR_TIMEOUT=300 androidContainer bash -c "./start_emu_headless.sh"

  • daemon not running; starting now at tcp:5037
  • daemon started successfully
    linux-gnu: emulator @nexus -no-window -no-snapshot -noaudio -no-boot-anim -memory 2048 -accel off -camera-back none -gpu off
    nohup: appending output to 'nohup.out'
    ==> Checking emulator booting up status 🧐
    ==> adb: no devices/emulators found, please wait ⠇

The issue was with the Linux AWS instance i used. The Linux AWS Instance should be a metal instance which supports hardware accelerations. The Emulator is up and running now

commented

I get the same result even if I run it locally on my Apple M2

M2 doesnt support nested virtualization unfortunately

commented

I get the same result even if I run it locally on my Apple M2

M2 doesnt support nested virtualization unfortunately

That's new, thanks! Should it be able to run on AWS non-metal if there's the -accel off flag?

commented

I get the same result even if I run it locally on my Apple M2

M2 doesnt support nested virtualization unfortunately

That's new, thanks! Should it be able to run on AWS non-metal if there's the -accel off flag?

Start with metal instance