如果这类项目继续发展下去，“手机”这个概念可能真的会消失。我们未来用的，可能根本不是“手机”，而是“运行在云上的 Android 实例”。

docker-android 做了一件很反常识的事：把完整 Android 系统，直接塞进 Docker 容器里运行。

不是简化版，不是模拟器壳子，而是： Android Emulator + ADB + QEMU + libvirt 的完整组合

结果一个“手机环境”，变成了一个可以部署的服务。

更夸张的是它的体积：Android API 33：约 1.97GB，API 28：约 1.46GB，极限精简后：138MB

一个“手机操作系统”，可以小到接近一个轻量服务镜像。 它带来的变化不是技术，而是定义层面的： Android 不再绑定设备 手机不再是“硬件形态” 操作系统开始变成“云端服务”

你甚至可以在服务器上直接： 跑 Android App 做自动化批量测试 远程控制 UI 构建虚拟设备集群

真正值得讨论的是这一点 当手机系统可以被容器化部署，那“手机厂商”的护城河还剩什么？

https://github.com/HQarroum/docker-android… #Android #Docker #云计算 #开源 #技术思考

HQarroum/docker-android

Source: https://github.com/HQarroum/docker-android

docker-android

A minimal and customizable Docker image running the Android emulator as a service.

Current version: 1.1.0

📋 Table of contents

• Features
• Description
• Usage
• See also

🔖 Features

• Minimal Alpine based image bundled with the Android emulator and KVM support.
• Bundles the Java Runtime Environment 11 in the image.
• Customizable Android version, device type and image types.
• Port-forwarding of emulator and ADB on the container network interface built-in.
• Emulator images are wiped each time the emulator re-starts.
• Runs headless, suitable for CI farms. Compatible with scrcpy to remotely control the Android screen.

🔰 Description

The focus of this project is to provide a size-optimized Docker image bundled with the minimal amount of software required to expose a fully functionning Android emulator that’s remotely controllable over the network. This image only contains the Android emulator itself, an ADB server used to remotely connect into the emulator from outside the container, and QEMU with libvirt support.

You can build this image without the Android SDK and without the Android emulator to make the image smaller. Below is a size comparison between some of the possible build variants.

📘 Usage

By default, a build will bundle the Android SDK, platform tools and emulator with the image.

with docker-compose:

docker compose up android-emulator

or with GPU acceleration

docker compose up android-emulator-cuda

or for example with GPU acceleration and google playstore

docker compose up android-emulator-cuda-store

with only docker

docker build -t android-emulator .

Keys

To run google_apis_playstore image, you need to have same adbkey between emulator and client.

You can generate one by running adb keygen adbkey, that generates 2 files - adbkey and adbkey.pub.

override them inside ./keys directory.

Running the container

Once the image is built, you can mount your KVM driver on the container and expose its ADB port.

Ensure 4GB of memory and at least 8GB of disk space for API 33.

docker run -it --rm --device /dev/kvm -p 5555:5555 android-emulator

Save data/storage after restart (wipe)

All avd save in docker dir /data, name for avd is android

docker run -it --rm --device /dev/kvm -p 5555:5555 -v ~/android_avd:/data android-emulator

Connect ADB to the container

The ADB server in the container will be spawned automatically and listen on all interfaces in the container. After a few seconds, once the kernel has booted, you will be able to connect ADB to the container.

adb connect 127.0.0.1:5555

Additionally, you can use scrcpy to control the screen of the emulator remotely. To do so, you simply have to connect ADB and run it locally.

By default, the emulator runs with a Pixel preset (1080x1920).

scrcpy

Customize the image

It is possible to customize the API level (Android version) and the image type (Google APIs vs PlayStore) when building the image.

By default, the image will build with API 33 with support for Google APIs for an x86_64 architecture.

This can come in handy when integrating multiple images as part of a CI pipeline where an application or a set of applications need to be tested against different Android versions. There are 2 variables that can be specified at build time to change the Android image.

• API_LEVEL - Specifies the API level associated with the image. Use this parameter to change the Android version.
• IMG_TYPE - Specifies the type of image to install.
• ARCHITECTURE Specifies the CPU architecture of the Android image. Note that only x86_64 and x86 are actively supported by this image.

The below example will install Android Pie with support for the Google Play Store.

docker build \
  --build-arg API_LEVEL=28 \
  --build-arg IMG_TYPE=google_apis_playstore \
  --build-arg ARCHITECTURE=x86 \
  --tag android-emulator .

Variables

Default variables

Disable animation

DISABLE_ANIMATION=false

Disable hidden policy

DISABLE_HIDDEN_POLICY=false

Skip adb authentication

SKIP_AUTH=true

Memory for emulator

MEMORY=8192

Cores for emulator

CORES=4

Extra flags to emulator

EXTRA_FLAGS=“-no-metrics -no-audio -partition-size=8192”

Mount an external drive in the container

It might be sometimes useful to have the entire Android SDK folder outside of the container (stored on a shared distributed filesystem such as NFS for example), to significantly reduce the size and the build time of the image.

To do so, you can specify a specific argument at build time to disable the download and installation of the SDK in the image.

docker build -t android-emulator --build-arg INSTALL_ANDROID_SDK=0 .

You will need mount the SDK in the container at /opt/android.

docker run -it --rm --device /dev/kvm -p 5555:5555 -v /shared/android/sdk:/opt/android/ android-emulator

Pull from Docker Hub

Different pre-built images of docker-android exist on Docker Hub. Each image variant is tagged using its the api level and image type. For example, to pull an API 33 image, you can run the following.

docker pull halimqarroum/docker-android:api-33

👀 See also

• The alpine-android project which is based on a different Alpine image.
• The docker-android project which offers a WebRTC interface to an Android emulator.