Ultimate Guide to install Anbox in any Arch-based distro(especially Garuda)

dr460nf1r3 · 3 May 2021 08:53

We need logs. But you are right, it doesnt work for me either right now. Looking at the systemd logs I get this:

Mai 03 10:44:53 T440p-void systemd[2536]: Started Anbox Session Manager.
Mai 03 10:44:54 T440p-void anbox[2543]: Failed to initialize EGL
Mai 03 10:44:54 T440p-void anbox[2543]: Failed to start container: Failed to start container: Failed to set config item lxc.group.devices.deny
Mai 03 10:44:54 T440p-void anbox[2543]: Lost connection to container manager, terminating.
Mai 03 10:44:54 T440p-void anbox[2543]: Container is not running
Mai 03 10:44:54 T440p-void anbox[2543]: Stack trace (most recent call last) in thread 2897:
Mai 03 10:44:54 T440p-void anbox[2543]: #5    Object "", at 0xffffffffffffffff, in
Mai 03 10:44:54 T440p-void systemd[2536]: anbox-session-manager.service: Main process exited, code=exited, status=1/FAILURE
Mai 03 10:44:54 T440p-void systemd[2536]: anbox-session-manager.service: Failed with result 'exit-code'.

which is pretty much the same issue reported here:

github.com/anbox/anbox

Anbox Couldn't work on lxc 4.0.8

opened 02:10PM - 01 May 21 UTC

STASWIT

1. Please check that no similar bug is already reported. Have a look on the list… of open bugs at https://github.com/anbox/anbox/issues 2. Make sure you are running the latest version of Anbox before reporting an issue. Update snap to latest: `snap refresh --devmode --edge anbox` 3. Make sure you have debug logs enabled: `sudo snap set anbox debug.enable=true` 4. Reproduce the error while debug logs enabled. 5. Run the anbox logs collection utility and attach the tar file. `sudo /snap/bin/anbox.collect-bug-info ` 6. ** Please paste the result of `anbox system-info` below:** <details> <summary>anbox system-info output</summary> ``` version: local-9de4e87 cpu: arch: x86 brand: Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz features: - aes - sse4_1 - sse4_2 - avx - avx2 os: name: Arch Linux version: snap-based: false kernel: version: Linux version 5.12.0-xanmod1-2 (makepkg@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Fri, 30 Apr 2021 11:40:51 +0000 binder: false ashmem: true graphics: egl: vendor: n/a version: n/a extensions: - n/a gles2: vendor: n/a vendor: n/a extensions: [] ``` </details> **Please describe your problem:** When I using latest anbox from ArchLinux(AUR), I followed ArchWiki's guidance, however, I have got this problem when using `$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity`: ``` [ 2021-05-01 13:58:55] [daemon.cpp:61@Run] [org.freedesktop.DBus.Error.ServiceUnknown] The name org.anbox was not provided by any .service files ``` Then I pressed `$ anbox session-manager`, it outputed: ``` [ 2021-05-01 13:59:33] [Renderer.cpp:104@initialize] Failed to initialize EGL [ 2021-05-01 13:59:33] [client.cpp:48@start] Failed to start container: Failed to start container: Failed to set config item lxc.group.devices.deny [ 2021-05-01 13:59:33] [session_manager.cpp:164@operator()] Lost connection to container manager, terminating. [ 2021-05-01 13:59:33] [daemon.cpp:61@Run] Container is not running Stack trace (most recent call last) in thread 23046: ``` **What were you expecting?:** I hope someone could fix it. **Additional info:** I'm Using `lxc-1:4.0.8-1` maybe the latest anbox haven't support it.

Best thing to do is to keep track of the issues

Edit: downgrading lxc to 4.0.6 is indeed a temporary fix, taken from above linked issue