Package Base Details: anbox-git

Git Clone URL: https://aur.archlinux.org/anbox-git.git (read-only, click to copy)
Submitter: irtimmer
Maintainer: irtimmer
Last Packager: irtimmer
Votes: 129
Popularity: 6.16
First Submitted: 2017-04-12 21:41
Last Updated: 2019-05-14 18:21

Pinned Comments

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-14 09:21

@subjectdenied Thanks. --gles-driver=host did the trick

subjectdenied commented on 2017-04-14 09:18

also on my skylake notebook, i have to use:

anbox session-manager --gles-driver=host

or else i get segfault

subjectdenied commented on 2017-04-14 09:17

https://github.com/anbox/anbox/issues/3#issuecomment-294023515
i just followed this short guide

GabMus commented on 2017-04-14 08:10

This is what I did:

Installed anbox-git from AUR (pulled the binder and ashmem modules with it)

sudo modprobe binder_linux
sudo modprobe ashmem_linux
export anboxdir=/home/gabmus/Documents/anbox
export datadir=$anboxdir/anbox-data
export rootdir=$datadir/rootfs
export androidimage=$anboxdir/android_1_amd64.img
sudo anbox container-manager --android-image=$androidimage --data-path=$datadir

At this point container-manager seems to work fine, it doesn't output anything and doesn't return until I Ctrl+c.

Then I run

anbox session-manager
(also tried with XDG_RUNTIME_DIR=$HOME/Documents/anbox/anbox-data anbox session-manager)

And I get
[EE 2017-04-14 08:03:56] [client.cpp:49@start] Failed to start container: Failed to start container: Failed to start container
[WW 2017-04-14 08:03:56] [session_manager.cpp:140@operator()] Lost connection to container manager, terminating.
[WW 2017-04-14 08:03:56] [session_manager.cpp:140@operator()] Lost connection to container manager, terminating.
[1] 6354 segmentation fault (core dumped) XDG_RUNTIME_DIR=$(pwd) anbox session-manager

Any idea?

guiniol commented on 2017-04-14 07:30

@subjectdenied Did you do anything to get the anbox session-manager to run? I'm getting a segfault

Tallix commented on 2017-04-14 07:19

I am getting the same error as @namoo4u and what @subjectdenied was formerly getting.

Attempting to run the container manager as non-root says that it should be started by the OS's init system. Does that have anything to do with it?

namoo4u commented on 2017-04-14 07:08

I run 'anbox container-manager' as root first and run 'anbox session-manager'
BUT it doesn't not work with this error

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

is there any solutions to fix it?

atondwal commented on 2017-04-14 03:58

@MichaelMcEntire @dansantos you need to run `anbox container-manager` as root first.

atondwal commented on 2017-04-14 03:58

@subjectdenied How did you get past the `Lost connection to container manager` error you were getting?

MichaelMcEntire commented on 2017-04-14 03:56

I have the same issue as dansantos.