Skip to content
Anbox is a container-based approach to boot a full Android system on a regular GNU/Linux system
Branch: xenial
Clone or download
Pull request Compare This branch is 57 commits ahead, 103 commits behind anbox:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
android android: forward logcat output to the container console Jun 12, 2018
cmake
data
debian Add new anbox tool for ubuntu touch Sep 15, 2018
docs Update install.md Jul 14, 2018
external
kernel Bring back kernel modules Aug 11, 2018
products Specify correct location for all files we're installing Aug 29, 2017
scripts cmds: allow users to change the container network configuration Sep 2, 2018
snap scripts: generate a zip instead of a tarball for our log archive Jul 23, 2018
src Hack to allow render of InputMethod under same window as requester Sep 16, 2018
tests
.clang-format Don't enforce column limit for our code style Jan 3, 2017
.gitignore
.travis.yml
AUTHORS Add List of authors Apr 5, 2017
Android.mk Implement audio support Jan 12, 2017
CMakeLists.txt Move ENABLE_TOUCH_INPUT option to before 'src' gets included Sep 9, 2018
COPYING.GPL Add proper README and COPYING file Jun 20, 2016
Jenkinsfile Add Jenkinsfile Jan 6, 2018
README.md scripts: use 18.04 as our new build environment Jun 12, 2018
cmake_uninstall.cmake.in added uninstall target to cmake to allow make uninstall operation Aug 18, 2017
cross-compile-chroot.sh

README.md

Snap Status Build Status

Anbox

Anbox is a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu. In other words: Anbox will let you run Android on your Linux system without the slowness of virtualization.

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 GNU/Linux-based platform.

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

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

Anbox is currently suited for the desktop use case but can be used on mobile operating systems like Ubuntu Touch, Sailfish OS or Lune OS too. However as the mapping of Android applications is currently desktop specific this needs additional work to supported stacked window user interfaces too.

The Android runtime environment ships with a minimal customized Android system image based on the Android Open Source Project. The used image is currently based on Android 7.1.1

Installation

See our installation instructions for details.

Supported Linux Distributions

At the moment we officially support the following Linux distributions:

  • Ubuntu 16.04 (xenial)
  • Ubuntu 18.04 (bionic)

However all other distributions supporting snap packages should work as well as long as they provide the mandatory kernel modules (see kernel/).

Install and Run Android Applications

TBD

Build from source

Requirements

To build the Anbox runtime itself there is nothing special to know. We're using cmake as build system. A few build dependencies need to be present on your host system:

  • libdbus
  • google-mock
  • google-test
  • libboost
  • libboost-filesystem
  • libboost-log
  • libboost-iostreams
  • libboost-program-options
  • libboost-system
  • libboost-test
  • libboost-thread
  • libcap
  • libsystemd
  • mesa (libegl1, libgles2)
  • glib-2.0
  • libsdl2
  • libprotobuf
  • protobuf-compiler
  • lxc (>= 3.0)

On an Ubuntu system you can install all build dependencies with the following command:

$ sudo apt install build-essential cmake cmake-data debhelper dbus google-mock \
    libboost-dev libboost-filesystem-dev libboost-log-dev libboost-iostreams-dev \
    libboost-program-options-dev libboost-system-dev libboost-test-dev \
    libboost-thread-dev libcap-dev libsystemd-dev libegl1-mesa-dev \
    libgles2-mesa-dev libglib2.0-dev libglm-dev libgtest-dev liblxc1 \
    libproperties-cpp-dev libprotobuf-dev libsdl2-dev libsdl2-image-dev lxc-dev \
    pkg-config protobuf-compiler 

We recommend Ubuntu 18.04 (bionic) with GCC 7.x as your build environment.

Build

Afterwards you can build Anbox with

$ git clone https://github.com/anbox/anbox.git
$ cd anbox
$ mkdir build
$ cd build
$ cmake ..
$ make

A simple

$ sudo make install

will install the necessary bits into your system.

If you want to build the anbox snap instead you can do this with the following steps:

$ mkdir android-images
$ cp /path/to/android.img android-images/android.img
$ snapcraft

The result will be a .snap file you can install on a system supporting snaps

$ snap install --dangerous --devmode anbox_1_amd64.snap

Run Anbox

Running Anbox from a local build requires a few more things you need to know about. Please have a look at the "Runtime Setup" documentation.

Documentation

You will find additional documentation for Anbox in the docs subdirectory of the project source.

Interesting things to have a look at

Reporting bugs

If you have found an issue with Anbox, please file a bug.

Get in Touch

If you want to get in contact with the developers please feel free to join the #anbox IRC channel on Freenode.

Copyright and Licensing

Anbox reuses code from other projects like the Android QEMU emulator. These projects are available in the external/ subdirectory with the licensing terms included.

The Anbox source itself, if not stated differently in the relevant source files, is licensed under the terms of the GPLv3 license.

You can’t perform that action at this time.