[Solved] Waydroid, anyone got it working?

[heikkikk]

Hi.
I wonder if anyone got app-containers/waydroid working.
Any hints on how to get it working are welcome.


waydroid session start
[17:04:41] OSError: container failed to start



I have:
app-containers/waydroid-1.4.0::guru USE="systemd -apparmor" PYTHON_SINGLE_TARGET="python3_10 -python3_9 -python3_11" 0 KiB

[fedeliallalinea]

Moved from Desktop Environments to Unsupported Software.
_________________
Questions are guaranteed in life; Answers aren't.

[heikkikk]

Got it working. Added this to package.use:
app-containers/lxc apparmor
app-containers/waydroid apparmor

[fedeliallalinea]

If you don't use apparmor you can follow instructions

[heikkikk]

Thanks Will try that.

[Dragonlord]

I'm trying to get waydroid working too but without any success so far. The problem seems to be an impossible permission situation.

"waydroid init" is required to be run as root. Using "su" to become root and running the command works.

"waydroid show-full-ui" is required to be run by user. If run by root I get an error "ERROR: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.". If I run it though as user I get the error "ERROR: WayDroid is not initialized, run "waydroid init"".

If I try to run "waydroid init" as user I though get "ERROR: Action "init" needs root access".

It is impossible to satisfy all these conditions at once. How is one supposed to run waydroid on GenToo?
_________________
DragonDreams: Leader and Head Programmer

[lindegur]

I also try to run waydroid. My know how on wayland and waydroid is pretty low.

During emerge I observed missing kernel options, additionally there are Android binder options.
So I updated my kernel.
I observed two new groups dnsmasq, lxc, so I added my regular user to it.
After installation I did

[an7h]

@Dragonlord
@lindegur

Here's pretty much everything required by Waydroid that isn't enabled in sys-kernel/gentoo-sources by default:
https://forums.gentoo.org/viewtopic-t-1165699.html

Notice that some options MUST be disabled in order for Waydroid to work correctly.

I also recommend emerging =app-containers/waydroid-9999 from the xira overlay. In the link above I mention the guru overlay, but this xira package allows updating to the latest version without issues (at least for me). Either way, when I was trying to get it to work properly, most problems would occur exactly because the kernel wasn't set up correctly. It was easy to confirm this by running Waydroid under with sys-kernel/gentoo-kernel-bin . Unfortunately the official documentation barely mentions anything about setting up a kernel for waydroid, which is why I posted a separate thread here on the forums.
_________________
If dreams were horses, beggars would ride.

[lindegur]

New Kernel with many new options, probably I will test sys-kernel/gentoo-kernel-bin es well but still same error.

[an7h]

@lindegur
You should try waydroid with sys-kernel/gentoo-kernel-bin just to see if this is an issue with the kernel config or not. Just to narrow down the source of the problem. If it works with sys-kernel/gentoo-kernel-bin , then there's something wrong with the kernel configuration. Earlier I would get that error when something wasn't enabled withing the netfilter. Also you can check the log by typing in waydroid log
_________________
If dreams were horses, beggars would ride.

[lindegur]

sys-kernel/gentoo-kernel-bin works. I get