docker-android VS android-emulator-container-scripts

If it was me I'd go with a docker-android container. You could go with Anbox or a virtual android machine, but if you just need to run one app, I think a docker container would be the way to go, since you could script it to open, run your app, and shut down.

I haven't personally tested this one, however, there is this project on github: https://github.com/budtmo/docker-android which uses containers.

I know this isn't the focus of the article, but this license provision in a linked project is outright strange.

>By using this software you agree that the following non-PII (non personally identifiable information) data will be collected, processed and used by the maintainers for the purpose of improving the docker-android project. Anonymisation with respect of the IP address means that only the first two octets of the IP address are collected.

https://github.com/budtmo/docker-android/blob/master/LICENSE...

How can you call a project Apache when you're forcing people to pay via their data ? Why is their no opt out option?

Absent that this seems like a great QA automation tool. Or a Tinder bot farm...

Alternatively, there are a few docker projects such as this one https://github.com/budtmo/docker-android that might work well. Haven’t tried it.

So far i was using docker-android i did use in my ubuntu during yesterday and was working fine

https://github.com/budtmo/docker-android this perhaps?

It's got absolutely nothing to do with the trustability of Android emulators. In fact I highly doubt they used something like Bluestacks, but rather something that can be chained with scripts like an Android docker container.

It looks like the thing you're trying to do was broken by PR 309, and I think it will work if you revert that change. (That is, change the word "exec" to "run" on line 247. Or put the word "eval" at the beginning of that line. Either one.)

I'm using a TURN server to route the Android SDK emulator's output (URL: https://github.com/google/android-emulator-container-scripts) to a browser window running on my local machine. However, the container that the emulator is running in won't start because it says that the TURN server configuration I passed it is incorrect.

I'm following this extremely short guide (https://source.android.com/devices/automotive/start/avd/cloud_emulator#troubleshooting) for android-emulator-container-scripts (https://github.com/google/android-emulator-container-scripts) to set up a TURN server to access my Android emulator from the open web, but when I boot up the emulator using Docker Compose after passing in my TURN server configuration using "export SNIPPET", I get the following error:

Also this issues thread on GitHub might be of some help

I've created a repo of android terraform scripts, that launch an instance of the android docker container in GCP. The scripts automatically

Yes, this is possible either on bare metal or if the hosting provider supports nested KVM. DuckDuckGo returns multiple hits, e.g. this. Regarding resources, you want at least 2-4 GB or RAM per emulated Android device. Accelerated GPU may also be a problem due to costs.