Package Details: anbox-git 1:r1358.84f0268-5

Git Clone URL: (read-only, click to copy)
Package Base: anbox-git
Description: Running Android in a container
Upstream URL:
Licenses: GPL3
Conflicts: anbox-launchers
Replaces: anbox-launchers
Submitter: irtimmer
Maintainer: C_Schmidpeter (ahmubashshir, chaotic-aur)
Last Packager: ahmubashshir
Votes: 151
Popularity: 3.42
First Submitted: 2017-04-12 21:41
Last Updated: 2022-01-14 19:33

Pinned Comments

ahmubashshir commented on 2022-01-09 17:34

Guys, please don't flag this package because of some other pkgbuilds, specially not if
any pkgbuild providing anbox-image fails to build, contact the maintainer of that faulty pkgbuild.

And remember, this is AUR(Arch User Repository), it doesn't provide any prebuilt package,
it only provides PKGBUILDs(recipe for building libalpm package).
You MUST rebuild the package yourself when the dependency gets soname bump
(when it complains about missing library).

irtimmer commented on 2018-01-19 10:35

WARNING: Before you go ahead and install Anbox on your system, please keep in mind that Anbox is not yet stable. Not every feature is working well yet. You will find bugs, see crashes and unexpected problems. As this is a Git package, patches should go upstream as they will not be bundled with the package.

guiniol commented on 2017-04-13 11:26

@EXL if you've got all that working, you should be able to 'anbox session-manager' and go from there. I couldn't get that to work but @subjectdenied seems to have got further along than me

subjectdenied commented on 2017-04-13 09:57

$ anbox session-manager

but it crashes with:

[EE 2017-04-13 09:56:07] [client.cpp:49@start] Failed to start container: Failed to start container: Failed to start container
[WW 2017-04-13 09:56:07] [session_manager.cpp:140@operator()] Lost connection to container manager, terminating.
[WW 2017-04-13 09:56:07] [session_manager.cpp:140@operator()] Lost connection to container manager, terminating.
[EE 2017-04-13 09:56:07] [daemon.cpp:58@Run] Container is not running

EXL commented on 2017-04-13 09:45

1. Install properties-cpp:
$ yaourt -S properties-cpp

2. Install process-cpp:
$ yaourt -S process-cpp
--- Edit PKBUILD and replace "_pkgver" to "pkgver" here:

3. Now install anbox-git:
$ yaourt -S anbox-git

4. Download android.img:
$ cd ~/Download/
$ wget

5. Run?
$ datadir=$HOME/Downloads/anbox-data
$ mkdir -p $datadir/rootfs
$ sudo anbox container-manager --android-image=/home/exl/Downloads/android_1_amd64.img --data-path=$datadir

@guiniol @subjectdenied
But what's next? Please help me.

guiniol commented on 2017-04-13 09:11

Next error:
Failed to open /usr//usr/lib/anbox/translators/ [/usr//usr/lib/anbox/translators/ cannot open shared object file: No such file or directory]

it's not looking in the right place

subjectdenied commented on 2017-04-13 09:01

android-image can be found here i guess:


guiniol commented on 2017-04-13 08:38

To launch the daemon, you need to run (this must be done before anbox session-manager):
anbox container-manager

If you get an error about 'No runtime directory specified' make sure 'XDG_RUNTIME_DIR' is set to something.

Now, all we need is the android.img

snowyyyy commented on 2017-04-13 08:08

[daemon.cpp:58@Run] Failed to connect to socket /run/anbox-container.socket: No such file or directory

guiniol commented on 2017-04-13 07:45

The kernel modules are in the package, however, they are not installed at the right place.
They are in

but they should be in

you can create a symlink (put whatever in the version) and then
dkms add anbox-modules-ashmem/<version>
dkms build anbox-modules-ashmem/<version>
dkms install anbox-modules-ashmem/<version>

The modules can then be loaded (ashmem_linux and binder_linux)

However, now it complains about `No runtime directory specified` and I have yet to figure out how to specify it

mufeed2000 commented on 2017-04-13 07:12

Has anyone got it actually running? Looks like we need kernel modules and a (very stripped down) android image. I can't seem to find either. Any help would be appreciated. :)

mufeed2000 commented on 2017-04-13 05:49

So, how do i use this? Installed it but session manager is not running because of the 2 kernel modules needed. How do i make that work?