Anbox is a container-based approach to boot a full Android system on a regular GNU/Linux system https://anbox.io
Find a file
2016-12-08 07:12:09 +01:00
android Handle window movement/resize/close on our side and not in Android 2016-12-08 07:08:47 +01:00
cmake Initial work 2016-06-14 11:34:17 +02:00
data Drop temporary file we don't want to track 2016-06-20 08:28:24 +02:00
debian debian: add libcap-dev as dependency a remove dbus-cpp version requirement 2016-07-08 17:43:41 +02:00
external Improve application manangement and create desktop entries for available app 2016-12-02 16:11:38 +01:00
kernel kernel: binder: use kallsyms_lookup_name for internal symbol access 2016-12-06 08:29:59 +01:00
scripts Bind mount cache/data on startup from writable space 2016-12-08 07:12:09 +01:00
src Map /dev/fuse to make Android volume manager happy 2016-12-08 07:10:52 +01:00
tests Move all qemu stuff in the correct subdirectory/namespace 2016-07-04 16:18:15 +02:00
.clang-format Reformat all code and use the Google cpp code style 2016-12-02 17:38:43 +01:00
.gitignore kernel: exclude further build artifacts 2016-12-06 08:30:13 +01:00
Android.mk Drop missing reference to removed intent class 2016-12-02 17:22:37 +01:00
CMakeLists.txt Install and load our translator libraries on startup 2016-09-30 17:21:15 +02:00
COPYING.GPL Add proper README and COPYING file 2016-06-20 09:37:16 +02:00
cross-compile-chroot.sh Initial work 2016-06-14 11:34:17 +02:00
README.md Extend README with installation and build details 2016-12-05 07:10:21 +01:00
snapcraft.yaml Use disk images instead of a rootfs tarball 2016-12-05 10:06:48 +01:00

Anbox

Anbox is container based approach to boot a full Android system.

Overview

Anbox uses Linux namespaces (user, pid, uts, net, mount, ipc) to run a full Android system in a container and provide Android applications on any platform.

The container itself does not run as root but as a unprivileged user. It just need to be able to perform a few operations to setup a container like spawning up new namespaces, chroot'ing to a rootfs etc.

Android inside the container has no direct access to any hardware. All hardware access is going through the anbox daemon. We're reusing what Android has implemented for the Qemu based emulator. The Android system inside the container uses different pipes to communicate with the host system and sends all hardware access commands through these. OpenGL rendering is provided through this.

For more details have a look at the following documentation pages:

Installation

Anbox is available as a snap in the public Ubuntu Store. Currently it is only available in the edge channel and requires to be installed in devmode as we don't have proper confinement for it in place yet.

Additionally you need to manually load the binder and ashmem kernel drivers everytime as we build them out-of-tree with a hack as this isn't officially supported. Before you start anbox you always need to execute

$ cd anbox $ scripts/load-kmods.sh

Anbox can be installed from the Ubuntu Store with

$ snap install --edge --devmode anbox

Afterwards run it with

$ anbox

After the first installation the container management service needs a few minutes to setup the container the first time before it is available.

Applications can be launched via the launch subcommand of the anbox binary. For example

$ anbox launch --package com.android.settings

Build from source

To build the Anbox runtime itself there is nothing special to know about. We're using cmake as build system.

$ mkdir build $ cd build $ cmake .. $ make

That will build the whole stack. A simple

$ make install

will install the necessary bits into your system.

Anbox reuses code from other projects like the Android Qemu emulator or bubblewrap (https://github.com/projectatomic/bubblewrap). These projects are available in the external/ subdirectory with the licensing terms included.

The anbox source itself (in src/) is licensed under the terms of the GPLv3 license:

Copyright (C) 2016 Simon Fels morphis@gravedo.de

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License version 3, as published by the Free Software Foundation.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranties of MERCHANTABILITY, SATISFACTORY QUALITY, or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.