2018-09-04 11:01:47 +01:00
Azure
-----
Make sure that the nodes, pods, containers for your emulators are generated within a **VM** of series **Dv3** or **Ev3** .
Reference: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization
2018-09-14 04:37:03 +01:00
AWS
-----
Make sure that containers for your emulators are generated within a EC2 Bare Metal Instance(i3.metal)
Reference: https://aws.amazon.com/jp/blogs/aws/new-amazon-ec2-bare-metal-instances-with-direct-access-to-hardware/
2018-10-05 16:12:55 +01:00
Google Cloud (GCE)
------------------
Make sure your instances for your emulators have Nested Virtualization enabled
2018-10-05 19:47:17 +01:00
Reference: https://cloud.google.com/compute/docs/instances/enable-nested-virtualization-vm-instances
One the disk and instance are created as [specified here ](https://cloud.google.com/compute/docs/instances/enable-nested-virtualization-vm-instances#enablenestedvirt ),
the emulator can be brought up as follows:
# Assume app.apk is in /tmp
docker run --privileged -d -e DEVICE="Samsung Galaxy S6" --volume /tmp:/APK \
2019-01-30 13:58:31 +00:00
--name android_em budtmo/docker-android-x86-8.1
2018-10-05 19:47:17 +01:00
docker exec android_em adb wait-for-device
docker exec android_em adb install /APK/app.apk
