cuttlefish-docker's Introduction

cuttlefish-docker

Run the Android Cuttlefish virtual device from within a Docker container. This still relies on the host's KVM support, so it's not fully isolated. (and the host will need to trust you, so this won't work on a cloud CI/CD system or similar without some control over the host)

Still very much a work-in-progress. (as in, it doesn't actually work yet)

Requirements

A Docker host that you have control over
On that host, working KVM (see here for instructions on how to check that)
- Note that this means your CPU needs to support some form of virtualization extensions
- This means you can't run this in a cloud VM, unless your cloud provider supports nested virtualization (Azure and Google Cloud both claim to, although this hasn't been tested on either)

Instructions

Download aosp_cf_x86_phone-img-6999531.zip and cvd-host_package.tar.gz as described in the official instructions.

On the host:

docker build --tag cuttlefish:latest .
docker run --network host --privileged -v /dev/log:/dev/log --device /dev/net/tun --device /dev/kvm --p 8444:8443 --user=0 -it cuttlefish:latest

Then, in the container:

cd cf
HOME=$PWD ./bin/launch_cvd -report_anonymous_usage_stats "y"

Limitations

It doesn't really work yet
Still need to figure out how to pass through hardware acceleration stuff
Path to aosp_cf_x86_phone-img is hardcoded to specific build ID
Requires manually running launch_cvd
- This should be automated with the start of the container
/dev/log from the host needs to be passed through to make crosvm happy; there should be a way around that
- rsyslogd is installed in the container, but it seems to need some configuration or something
The code in the container is run with uid 0 (aka root)
- This should be fixable? Might need to change the usermod commands in the Dockerfile though.
Data persistence doesn't really work yet
- Should be using a bind mount or volume to save the VM data

Recommend Projects