Came across this very useful project. It provides Docker images with Android running directly in Docker, without qemu or an emulator. I've never seen this before, all other solutions that I'm aware of either run the Android emulator in Docker or use qemu directly (like Anbox).<p>Advantage of this is that it's very lightweight and does not require VT-X or AMD-V, ideal for running in cloud environments that typically do not expose this CPU capability.
What exactly is Docker enabling here beyond a Docker workflow, which is quite orthogonal to the presence of a vm or emulator?<p>Isn't the enabling technology here just kernel-level android bits? Docker is fluff, yet ends up dominating the headline.
Interesting concept but seems to require custom android-specific kernel modules (ashmem, binderfs), which means the android containers aren't very containerized but leak into the host kernel.
Don't forget waydroid: <a href="https://waydro.id/" rel="nofollow">https://waydro.id/</a> . Last time I tried, it worked reasonably well.
This is interesting, but I don’t see this as something for use in development of Android apps. Given all Android’s quarks and fragmentation the use of real devices and Google’s emulators will provide a better surface to catch bugs during dev. What’s the primary use case for these containerized versions of Android?
How is this accomplished? Is this using Anbox or something similar
I don't understand how the Dockerfiles linked here end up running an instance of Android.
For development work I use the default Android emulator that comes with Android Studio.<p>Are any of these ones superior in terms of performance, resource utilization, etc? The cloud angle is mildly interesting although in my specific use-case I'd probably just end up paying for a service that can provide access to emulators in the cloud.<p>Is there more scope to do things like automating inputs etc this way? How would one go about that?
Trying to fix some Rust docker builds that are being killed by QEMU on Apple Silicon right now. I always believed Docker was cross platform, I had no idea how much of a pain it can be to use with buildx and --platform to get stuff working. SIGSEGV errors at random points, non-deterministic errors, <i>GAH!</i>