Arch Linux User Repository

Before install Waydroid, make sure that your kernel supports binder and ashmem module (currently only linux-zen does)

Keep in mind that Waydroid only works with Wayland compositors. It also does not work yet with proprietary NVIDIA driver.

After install waydroid and waydroid-image, run this command to initialize the container:

# waydroid init

Then the container can be started via waydroid-container.service. The official project group/channel can be found on:

• Matrix: https://matrix.to/#/#waydroid:connolly.tech
• Telegram: https://t.me/waydroid

@dcryptr try the solution in this thread.

https://github.com/waydroid/waydroid/issues/631

@dangerdev well, i've tried linux-zen. same error messages.

my network is rather down, will edit this comment after trying uninstall / install waydroid.

edit:

nope, nothing works anymore.

reinstall waydroid, changing kernel, reinstall anbox-modules / binder_linux ...

before update, it runs well with linux-lts version 5.* and linux version 6.1.12

but, now the container not even starting properly with this error with dmesg,

[45115.884915] init: SetupMountNamespaces failed: Read-only file system

and this error with waydroid log,

lxc-start: waydroid: ../src/lxc/conf.c: run_buffer: 322 Script exited with status 126
lxc-start: waydroid: ../src/lxc/start.c: lxc_end: 985 Failed to run lxc.hook.post-stop for container "waydroid"

could someone tell me how to get more info / logs ?

@dcryptr Have you tried using the linux-zen kernel ? In archwiki I found this:

Using Linux-Zen The linux-zen kernel includes the necessary modules. This might be the most comfortable way, as you do not have to compile the kernel (which takes a long time) and will receive updated versions regularly.

@C_Schmidpeter it is indeed strange, and after i check dmesg this is the (partial) message with error;

...
[45115.883487] init: Running restorecon...
[45115.883645] init: Created socket '/dev/socket/property_service', mode 666, user 0, group 0
[45115.884915] init: SetupMountNamespaces failed: Read-only file system
[45115.885404] init: InitFatalReboot: signal 6
[45115.890082] init: #00 pc 00000000000e40bd  /system/bin/init (android::init::InitFatalReboot(int)+205)
[45115.890090] init: #01 pc 000000000006b4b0  /system/bin/init (android::init::InitAborter(char const*)+32)
[45115.890097] init: #02 pc 0000000000019cfc  /system/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char 
const*)>&&)::$_3::__invoke(char const*)+60)
[45115.890103] init: #03 pc 00000000000192a0  /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+368)
[45115.890108] init: #04 pc 00000000000aed25  /system/bin/init (android::init::SecondStageMain(int, char**)+13653)
[45115.890113] init: #05 pc 000000000003798c  /system/bin/init (main+300)
[45115.890117] init: #06 pc 0000000000093bc8  /system/lib64/bootstrap/libc.so (__libc_init+104)
[45115.890121] init: Reboot ending, jumping to kernel
...

things i've tried before: 1. full upgrade system 2. change from anbox-modules-dkms to binder_linux 3. change from linux-lts to linux

well, when i try to change back to anbox-modules-dkms i get fatal error while build. for now i'm using linux-6.1.2 and binder_linux-dkms.

where i can get more debug info so i can get to know what is causing the error?

dbus-python should be its dependence

@dcryptr Strange, v1.4 works for me

Sorry, why am i getting this error after i upgrade to waydroid-1.4.0?

lxc-start: waydroid: ../src/lxc/conf.c: run_buffer: 322 Script exited with status 126
lxc-start: waydroid: ../src/lxc/start.c: lxc_end: 985 Failed to run lxc.hook.post-stop for container "waydroid"

it worked perfectly before with version 1.3.4. is it a problem with python-gbinder?

which command is no longer required in waydroid 1.4.0, it can be removed from dependencies.

Sorry everyone for not updating in a week! I was busy with other stuffs. So I'll be back on working now.

You need to run pip3 install Cython before installing this package. It is needed to compile python-gbinder.