I've installed anbox from the default repositories.
The ashmem
and binder
modules are loaded:
$ lsmod | grep _linux
binder_linux 163840 0
ashmem_linux 20480 0
The anbox-container-manager
system service is running:
$ systemctl status anbox-container-manager
● anbox-container-manager.service - Anbox Container Manager
Loaded: loaded (/lib/systemd/system/anbox-container-manager.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-11-08 12:17:33 GMT; 7min ago
Docs: man:anbox(1)
Process: 1239 ExecStartPre=/sbin/modprobe ashmem_linux (code=exited, status=0/SUCCESS)
Process: 1250 ExecStartPre=/sbin/modprobe binder_linux (code=exited, status=0/SUCCESS)
Process: 1265 ExecStartPre=/usr/share/anbox/anbox-bridge.sh start (code=exited, status=0/SUCCESS)
Main PID: 1334 (anbox)
Tasks: 9 (limit: 4915)
Memory: 11.3M
CGroup: /system.slice/anbox-container-manager.service
└─1334 /usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox
Nov 08 12:17:33 frog systemd[1]: Starting Anbox Container Manager...
Nov 08 12:17:33 frog systemd[1]: Started Anbox Container Manager.
But when I try to start the session manager it claims the kernel modules are not installed:
$ anbox session-manager
[ 2019-11-08 12:25:39] [session_manager.cpp:130@operator()] Failed to start as either binder or ashmem kernel drivers are not loaded
Is this a known issue?
Same error here today, my system:
One thing I've noticed is that although modprobe works ok, only
/dev/ashmem
is created...The kernel modules are there, but /dev/binder isn't—because that's not the way the
binder_linux
module works, now. morphis however consider it not a bug, because they have a pull request to make anbox work with the currentbinder_linux
module. As far as I can tell, you should be able to make it work with the "edge" channel of the snap. I.e.,but my experience with snaps is non-existent