Bug#973487: anbox: Anbox can't start: "/run/anbox-container.socket: No such file or directory"

[Shengjing Zhu]

On Mon, Nov 2, 2020 at 5:12 AM Teodoro Coluccio
 wrote:
>
> ok, after these steps and after rebooting, everything works fine.
>

Usually you don't need to reboot. I think restarting
anbox-container-manager.service
may do the trick as well.

https://salsa.debian.org/zhsj/anbox/-/commit/1b13e60a1a704a80bf832d1e0097a8977d7d0bea

-- 
Shengjing Zhu

Bug#973487: anbox: Anbox can't start: "/run/anbox-container.socket: No such file or directory"

[Teodoro Coluccio]

ok, in summary, I gave the following commands:
1) loaded the 2 kernel modules with:
sudo modprobe binder_linux
sudo modprobe ashmen_linux
2) downloaded this android image: 
https://build.anbox.io/android-images/2018/07/19/, renamed to android.img and 
moved to /var/lib/anbox/
3) started the anbox-container-manager.service and the 
anbox-session-manager.service with:
sudo systemctl start anbox-container-manager.service
systemctl --user start anbox-session-manager.service
4) Finally, after these steps and after rebooting, everything works fine.
Thank you for your support.

Regards
Teo

Bug#973487: anbox: Anbox can't start: "/run/anbox-container.socket: No such file or directory"

[Shengjing Zhu]

On Sun, Nov 1, 2020 at 12:03 AM Teo  wrote:
>
> Package: anbox
> Version: 0.0~git20200526-1+b2
> Severity: important
> Tags: patch
> X-Debbugs-Cc: teodoro777.coluc...@live.com
>
> I installed anbox, then I loaded ashmen and binder kernel drivers with
> "modprobe ashmem_linux" and "modprobe binder_linux". So I enabled and started
> the service with "systemctl enable anbox-container-manager.service" and
> "systemctl start anbox-container-manager.service", but but it continues to
> crash at the start on a graphic level.
> Indeed with "anbox session-manager" it returns "[daemon.cpp:61@Run] Failed to
> connect to socket /run/anbox-container.socket: No such file or directory".

It means your anbox-container-manager.service is not started successfully.
Have you followed the instruction in /usr/share/doc/anbox/README.Debian?

-- 
Shengjing Zhu

Bug#973487: anbox: Anbox can't start: "/run/anbox-container.socket: No such file or directory"

[Teo]

Package: anbox
Version: 0.0~git20200526-1+b2
Severity: important
Tags: patch
X-Debbugs-Cc: teodoro777.coluc...@live.com

I installed anbox, then I loaded ashmen and binder kernel drivers with
"modprobe ashmem_linux" and "modprobe binder_linux". So I enabled and started
the service with "systemctl enable anbox-container-manager.service" and
"systemctl start anbox-container-manager.service", but but it continues to
crash at the start on a graphic level.
Indeed with "anbox session-manager" it returns "[daemon.cpp:61@Run] Failed to
connect to socket /run/anbox-container.socket: No such file or directory".



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages anbox depends on:
ii  init-system-helpers 1.58
ii  iptables1.8.5-3
ii  libboost-filesystem1.71.0   1.71.0-7+b1
ii  libboost-iostreams1.71.01.71.0-7+b1
ii  libboost-log1.71.0  1.71.0-7+b1
ii  libboost-program-options1.71.0  1.71.0-7+b1
ii  libboost-thread1.71.0   1.71.0-7+b1
ii  libc6   2.31-4
ii  libegl1 1.3.2-1
ii  libgcc-s1   10.2.0-15
ii  libgles21.3.2-1
ii  liblxc1 1:4.0.4-5
ii  libprotobuf-lite23  3.12.3-2+b1
ii  libsdl2-2.0-0   2.0.12+dfsg1-4
ii  libsdl2-image-2.0-0 2.0.5+dfsg1-2
ii  libstdc++6  10.2.0-15
ii  libsystemd0 246.6-2
ii  lxc 1:4.0.4-5

Versions of packages anbox recommends:
ii  dbus-user-session  1.12.20-1

anbox suggests no packages.

-- no debconf information