You are not logged in.

#1 2020-11-06 13:52:24

snap.ve
Member
Registered: 2020-04-02
Posts: 65

[SOLVED] Anbox isn't working

Howdy! Yesterday i was install the anbox like that manual said. But when i start program with default params like

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

Console writhe this message

[daemon.cpp:61@Run] [org.freedesktop.DBus.Error.ServiceUnknown] The name org.anbox was not provided by any .service files

Who faced the same problem?

Last edited by snap.ve (2020-11-07 23:16:17)

Offline

#2 2020-11-06 14:12:17

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 8,587

Re: [SOLVED] Anbox isn't working

What is the output of

$ systemctl status anbox-container-manager.service

?


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#3 2020-11-06 15:08:04

snap.ve
Member
Registered: 2020-04-02
Posts: 65

Re: [SOLVED] Anbox isn't working

Lone_Wolf wrote:

What is the output of

$ systemctl status anbox-container-manager.service

?

● anbox-container-manager.service - Anbox Container Manager
     Loaded: loaded (/usr/lib/systemd/system/anbox-container-manager.service; e>
     Active: active (running) since Fri 2020-11-06 18:06:32 MSK; 28s ago
   Main PID: 667 (anbox)
      Tasks: 9 (limit: 19018)
     Memory: 15.3M
     CGroup: /system.slice/anbox-container-manager.service
             └─667 /usr/bin/anbox container-manager --daemon --privileged --dat>

Nov 06 18:06:32 system systemd[1]: Started Anbox Container Manager.
lines 1-10/10 (END)

Offline

#4 2020-11-07 22:54:07

snap.ve
Member
Registered: 2020-04-02
Posts: 65

Re: [SOLVED] Anbox isn't working

The problem is actual. More detailed dialogue here

Offline

#5 2020-11-07 23:14:43

snap.ve
Member
Registered: 2020-04-02
Posts: 65

Re: [SOLVED] Anbox isn't working

I found a solution! First of all, I ran the anbox session-manager command to understand what the log produces. They said "Failed to start as either binder or ashmem kernel drivers are not loaded" That's strange because in manual page said - just run modprobe command for activate the binder and ashmem driver. As it turned out, this was not enough and the manual misinformed me. The solution to the problem was adding the binder_linux ashmem_linux parameter to the modules section in mkinitcpio.conf file and rebuilding the bootloader with the mkinitcpio -P command. Now all woks!

Offline

Board footer

Powered by FluxBB