Anbox doesn't start, /dev/binder isn't created (20.04)

[Dima]

There is one of related bug reports
https://github.com/anbox/anbox-modules/issues/20
Some people say that snap edge version does work. But I get segfault with the both snap versions.
Probably deb version doesn't work after kernel upgrade.

$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
[ 2020-06-23 16:34:25] [daemon.cpp:61@Run] Application manager service is not running yet

$ anbox session-manager
[ 2020-06-23 16:35:01] [session_manager.cpp:133@operator()] Failed to start as either binder or ashmem kernel drivers are not loaded

$ lsmod | grep binder
binder_linux 180224 0

$ lsmod | grep ashmem
ashmem_linux 20480 0

$ ls -1 /dev/{ashmem,binder}
ls: cannot access '/dev/binder': No such file or directory
/dev/ashmem

I use default kernel version (generic, non-hwe).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: anbox 0.0~git20191115-1build1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXDE
Date: Tue Jun 23 19:23:43 2020
EcryptfsInUse: Yes
SourcePackage: anbox
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[doru001 (headset001)]

Could be this reason?
https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS

[rdrpenguin (rdrpenguin04)]

Same problem on Linux Mint 20.

[Doug Maurer (krzydoug)]

Confirmed the answer here resolved this issue on 20.04
https://superuser.com/a/1590708/511639

[David Baumann (davidbaumann)]

See the available beta version here: https://github.com/anbox/anbox/blob/master/docs/install.md#verify-that-kernel-modules-are-loaded

It works on my Ubuntu 20.04 now.

[fatalfeel (fatalfeel)]

try this souurce build it on ubuntu
https://github.com/fatalfeel/binderubuntu

[Knickers Brown (metta-crawler)]

/dev/binder is obsolete. Installing the binder_linux module creates a filesystem type now.

https://brauner.github.io/2019/01/09/android-binderfs.html

Summary (excerpts, see the blog entry link for more):
Problem 1: Using the misc major Device Number
Problem 2: Containers and IPC namespaces
To solve both problems we came up with a solution that I presented at the Linux Plumbers Conference in Vancouver this year.
Android binderfs is a tiny filesystem that allows users to dynamically allocate binder devices, i.e. it allows to add and remove binder devices at runtime.

mkdir /dev/binderfs
mount -t binder binder /dev/binderfs

See also
https://askubuntu.com/questions/1267990/ls-1-dev-ashmem-binder-yields-anticipated-result-for-dev-ashmem-but-an-err