You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am on MacOS X.
After googleing around i found that i need a KVM ubutu machine to resolve this machine but not sure what are the steps i should take to resolve this issue on MacOS X. So far i have done following steps
Install VirtualBox with ubutu image.
Again tried above given docker command but with no help.
Can you please help resolve this? Or guide what is required to resolve this issue.
The text was updated successfully, but these errors were encountered:
It won't work in virtual machine because VirtualBox doesn't support nested hardware-accelerated virtualization. There are other virtual machines that support passing VT-x extension to their guests but it would be very inefficient setup (VM inside VM);
To start AVD on your host you need to make sure that /dev/kvm exists. If it doesn't, you will need to enable VT-x and install/enable Intel HAXM. These answers may help;
If Docker runs natively on macOS, it should be possible to mount /dev/kvm into container the same way as on Linux (--device /dev/kvm). However, I don't have any devices with macOS, so I can't test it myself;
This container is more suitable for headless setups on Linux servers. On desktop you might want to use AVD without Docker (directly or via Android Studio). It will have the same functionality as well as faster UI and more flexibility.
Hello,
I was follow most steps listed here but it seems below command is not working for me.
docker run -it --rm --device /dev/kvm -p 5554:5554 -p 5555:5555 thedrhax/android-avd
I am on MacOS X.
After googleing around i found that i need a KVM ubutu machine to resolve this machine but not sure what are the steps i should take to resolve this issue on MacOS X. So far i have done following steps
Can you please help resolve this? Or guide what is required to resolve this issue.
The text was updated successfully, but these errors were encountered: