Skip to end of metadata
Go to start of metadata


IEC Type3 mainly focus on Android Application running on edge ARM Cloud architecture with GPU/ vGPU Management. Also, ARM cloud games need to have the basic features of "cloud”, such as flexibility , availability everywhere. Based on cloud infrastructure optimized for android application, providing ARM application services.

This document describes the deployment architecture, construction and use of anbox Android container environment. Describes the environment configuration, code download, build and how to use it

How to use this document

This document provides a general deployment about about the contruction of Android container environment, including pre-installation requirements, installation step, uninstall and troubleshooting.

Deployment Architecture

Pre-Installation Requirements

  • Hardware Requirements

Processor model

2*Kunpeng  920 processor




10*2.5 inch SAS/SATA/SSD or 8*2.5 inch  NVMe SSD


1 onboard network card, each card supports 4*GE port or 4*10GE port or 4*25GE port

Power Supply

 Power 100~240V AC,240V DC


447 mm x 490 mm x 86.1 mm

ARM Server satisfies the Arm Server Ready certified.

  • Software Perequisites


  • Database Perequisites

schema scripts: N/A

  • Other Installation Requirements
    • Jump Host Requirements:N/A
    • Network Requirements: N/A
    • Bare Metal Node Requirements :N/A
    • Execution Requirements (Bare Metal Only) :N/A

Installation High-Level Overview

  • Bare Metal Deployment Guide 

    • Install Bare Metal Jump Host : N/A

    • Creating a Node Inventory File: N/A

    • Creating the Settings Files: N/A

    • Running: N/A

  • Virtual Deployment Guide

    • Install Debian 10 OS on Server
  • Get Os Image from

    • Install kubectl on Linux

    Install kubectl binary with curl on Linux

    1. Download the latest release with the command:
      curl -LO`curl -s`/bin/linux/amd64/kubectl
      To download a specific version, replace the $(curl -s portion of the command with the specific version.For example, to download version v1.18.0 on Linux, type:
      curl -LO
    2. Make the kubectl binary executable.
      chmod +x ./kubectl
    3. Move the binary in to your PATH.
      sudo mv ./kubectl /usr/local/bin/kubectl
    4. Test to ensure the version you installed is up-to-date:
      kubectl version --client

    5. Install Anbox

    Anbox is a free and open-source compatibility layer that aims to allow mobile applications and mobile games developed for Android to run on GNU/Linux distributions. 

    To install Anbox your system need to support snaps. We do not officially support any other distribution method of Anbox at the moment but there are community made packages for various distributions (e.g. Arch Linux). However please keep in mind that the Anbox project can give not support them and its solely in the responsibility of the community packager to keep up with upstream development and update the packaging to any new changes. Please feel free to report still any bugs you encounter as they may not be related to the packaging.If you don’t know about snaps yet head over to to get an introduction of what snaps are, how to install support for them on your distribution and how to use them.The installation of Anbox consists of two steps.

    1. Install necessary kernel modules
    2. Install the Anbox snap

    1、Install kernel modules

    To install the necessary kernel modules, please read Install Kernel Modules.

    After correct installation you should have two new nodes in your systems /dev directory:

    $ ls -1 /dev/{ashmem,binder}

    2、Install the Anbox snap

    The second step will install the Anbox snap from the store and will give you everything you need to run the full Anbox experience.

    Installing the Anbox snap is very simple:

    $ snap install --devmode --beta anbox

    If you didn’t logged into the Ubuntu Store yet, the snap command will ask you to use sudo snap … in order to install the snap:

    $ sudo snap install --devmode --beta anbox

    At the moment we require the use of –devmode as the Anbox snap is not yet fully confined. Work has started with the upstream snapd project to get support for full confinement.

    As a side effect of using –devmode the snap will not automatically update. In order to update to a newer version you can run:

    $ snap refresh --beta --devmode anbox

    Information about the currently available versions of the snap is available via:

    $ snap info anbox

    • Standard Deployment Overview :N/A
    • Snapshot Deployment Overview:N/A
    • Special Requirements for Virtual Deployments
    • Install Jump Host: N/A
      • Verifying the Setup - VMs:N/A
  • Upstream Deployment Guide

    • Upstream Deployment Key Features :N/A
    • Special Requirements for Upstream Deployments :N/A
    • Scenarios and Deploy Settings for Upstream Deployments :N/A
    • Including Upstream Patches with Deployment:N/A
    • Running: N/A
    • Interacting with Containerized Overcloud: N/A

Verifying the Setup as defined the Akraino validation feature project plus any additional testing specific to the blue print

Developer Guide and Troubleshooting

  • Utilization of Images


  • Post-deployment Configuration


  • Debugging Failures 


  • Reporting a Bug


Uninstall Guide

The following method only uses snap to install Anbox. If you want to delete Anbox from the system, you must first delete snap.

Attention:Remove all data stored in the snapshot from the system:

$ snap remove anbox

After deleting the snapshot, you must also delete the installed kernel modules (if installed):

$ sudo apt install ppa-purge

$ sudo ppa-purge ppa:morphis/anbox-support

Upon completion, Anbox will be removed from your system.


  • If kernels modules successfully loaded, service is running fine, and yet Anbox won't launch with Application manager service is not running yet. Check for the message No space left on device - Failed to enter cgroup in /var/lib/anbox/logs/container.log, you may be running into see this issue:
  • If container started failed

Before the container is started, session-manager needs to be started on the host to start x, input, adb and other related services, and then the container may started successful.

  • To build the Anbox runtime itself there is nothing special to know. but when we use 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)
    * libglm
    * libsdl2
    * libprotobuf
    * protobuf-compiler
    * python2
    * lxc (>= 3.0)


  • Blue Print Package Maintenance

    • Software maintenance: N/A 
    • Hardware maintenance:N/A
  • Blue Print Deployment Maintenance :N/A

Frequently Asked Questions






Definitions, acronyms and abbreviations


  • No labels