Thanks Shengjing, 1) the readme says "In order to run Android system inside container, you need two kernel modules: ashmem_linux and binder_linux. Since Debian kernel 4.17, these two modules are enabled. You can find theme at, /lib/modules/`uname -r`/kernel/drivers/android/binder_linux.ko and /lib/modules/`uname -r`/kernel/drivers/staging/android/ashmem_linux.ko." but it does not say how to load these mobules; it turned out to be "modprobe binder_linux" and "modprobe ashmem_linux" but this took several guesses (I tried the full path too). Perhaps the readme should be clarified to include this correct command.
2) if configuration is required, perhaps an ncurses wizard similar to that of mysql (where it sets the root password) should be offered, or at least a dialog "this package requires additional configuration, please check the readme here at /usr/share/doc/anbox/ for details" should be shown 3) Continuing usage after following the steps suggested in the readme, /var/lib/anbox$ sudo lsmod | grep linux ashmem_linux 16384 0 binder_linux 135168 0 /var/lib/anbox$ file android.img android.img: Squashfs filesystem, little endian, version 4.0, 325898705 bytes, 2116 inodes, blocksize: 131072 bytes, created: Fri Jul 20 01:19:03 2018 /var/lib/anbox$ anbox session-manager [ 2018-12-29 05:57:18] [daemon.cpp:61@Run] Failed to connect to socket /run/anbox-container.socket: No such file or directory /var/lib/anbox$ -- Svetlana
