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

Traceback (most recent call last):
  File "/home/jccc/.cache/yay/python-gbinder/src/python-gbinder/setup.py", line 2, in <module>
    from distutils.core import setup, Extension
ModuleNotFoundError: No module named 'distutils'
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: python-gbinder-exit status 4
==> Making package: waydroid 1.4.3-1 (Fri 08 Nov 2024 01:54:49 PM CST)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> python-gbinder
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
 -> error making: waydroid-exit status 8
 -> Failed to install the following packages. Manual intervention is required:
python-gbinder - exit status 4
waydroid - exit status 8

distutils is deprecated with removal planned for Python 3.12.

Please make GTK optional, It's not needed for waydroid to operate.

Adding ibt=off to the vanilla kernel lowers security of your system. You have to switch to linux-zen which has dynamic support of IBT

error: Could not read a41a171e4074cefa669654ded8002dc1206ab0d7
==> ERROR: Failure while creating working copy of waydroid git repo

I'm having the same issue as @sokol99.

I keep get this error while building and am stuck:

error: Could not read a41a171e4074cefa669654ded8002dc1206ab0d7

It's something in your installed packages, then. I was able to build libglibutil-1.0.76-1 -> libgbinder-1.1.38-1 -> python-gbinder-1.1.2-1 -> waydroid-1.4.2-1 using devtools and a custom repo to hold each successive dependency.

==> Starting build()...
Traceback (most recent call last):
  File "/home/sam/.cache/yay/python-gbinder/src/python-gbinder/setup.py", line 2, in <module>
    from distutils.core import setup, Extension
ModuleNotFoundError: No module named 'distutils'
==> ERROR: A failure occurred in build().

I'm also having this issue as of April 18th, 2024.

Traceback (most recent call last):
File "/home/millions/.cache/yay/python-gbinder/src/python-gbinder/setup.py", line 2, in <module>
from distutils.core import setup, Extension
ModuleNotFoundError: No module named 'distutils'
==> ERROR: A failure occurred in build().
Aborting...
-> error making: python-gbinder-exit status 4


error while building

The comment on page 5 about binderfs should probably be pinned too. It's also linked to externally, but doesn't work as a link because it keeps moving pages back.

Edit: My bad, it's just that the Waydroid scripts try to modprobe binder_linux to detect if it's "loaded" rather than simply checking if the binder-control node exists already. My current kernel only offers the user facing options to either not build binder support, or compile it in, not as a module.

✗ waydroid session start  
[18:14:55] RuntimeError: Command failed: % /usr/lib/waydroid/data/scripts/waydroid-net.sh start

~   at 18:14:55 
Δ /usr/lib/waydroid/data/scripts/waydroid-net.sh start
vnic is waydroid0
RTNETLINK answers: Operation not permitted
Failed to setup waydroid-net

anyone have any idea?