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

It just doesn't start on latest Arch:

(014577) [19:31:22] Failed to start Clipboard manager service, check logs (014577) [19:31:27] Clipboard service is not even started (013106) [19:31:27] session manager stopped, stopping container and waiting...

You can try to run this command to grep for kernel options required

zcat /proc/config.gz| grep 'ANDROID_BINDER_DEVICES\|ASHMEM'

If it return blank (or your kernel does not support one of the option) then your kernel doesn't work with Waydroid.

Anyway, core/linux (what you're using now) doesn't support Android options.

How do I found out if the kernel supports binder? It's 5.14.6-arch1-1.

I did what robxu9 said about boot cmdline, rebooted but it keeps returning this eror: Module binder_linux not found I searched the repos for binder_linux but couldn't find any package with that specific name.

If you have binderfs (via linux-zen), it usually initialises empty. It looks like waydroid is currently not calling binder-control to automatically set up the devices, so if you're running into:

ERROR: Binder node "binder" for waydroid not found

Append the following to your boot cmdline and restart:

binder.devices=binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder

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

Always getting WARNING: Service manager /dev/binder has died

Container does'nt start

Failed to setup waydroid-net.
(003483) [14:30:35] % sudo waydroid-sensord /dev/hwbinder
(003483) [14:30:35] run: ['sudo', 'waydroid-sensord', '/dev/hwbinder']
(003483) [14:30:35] New background process: pid=3527, output=background
(003483) [14:30:35] % sudo umount /var/lib/waydroid/rootfs/vendor/waydroid.prop
(003483) [14:30:35] run: ['sudo', 'umount', '/var/lib/waydroid/rootfs/vendor/waydroid.prop']
sudo: waydroid-sensord: command not found
(003483) [14:30:35] % sudo umount /var/lib/waydroid/rootfs/vendor
(003483) [14:30:35] run: ['sudo', 'umount', '/var/lib/waydroid/rootfs/vendor']
(003483) [14:30:35] % sudo umount /var/lib/waydroid/rootfs
(003483) [14:30:35] run: ['sudo', 'umount', '/var/lib/waydroid/rootfs']
(003483) [14:30:35] % sudo mount /usr/share/waydroid-extra/images/system.img /var/lib/waydroid/rootfs
(003483) [14:30:35] run: ['sudo', 'mount', '/usr/share/waydroid-extra/images/system.img', '/var/lib/waydroid/rootfs']
(003483) [14:30:35] % sudo mount -o remount,ro /usr/share/waydroid-extra/images/system.img /var/lib/waydroid/rootfs
(003483) [14:30:35] run: ['sudo', 'mount', '-o', 'remount,ro', '/usr/share/waydroid-extra/images/system.img', '/var/lib/waydroid/rootfs']
(003483) [14:30:35] % sudo mount /usr/share/waydroid-extra/images/vendor.img /var/lib/waydroid/rootfs/vendor
(003483) [14:30:35] run: ['sudo', 'mount', '/usr/share/waydroid-extra/images/vendor.img', '/var/lib/waydroid/rootfs/vendor']
(003483) [14:30:35] % sudo mount -o remount,ro /usr/share/waydroid-extra/images/vendor.img /var/lib/waydroid/rootfs/vendor
(003483) [14:30:35] run: ['sudo', 'mount', '-o', 'remount,ro', '/usr/share/waydroid-extra/images/vendor.img', '/var/lib/waydroid/rootfs/vendor']
(003483) [14:30:35] % sudo mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop
(003483) [14:30:35] run: ['sudo', 'mount', '-o', 'bind', '/var/lib/waydroid/waydroid.prop', '/var/lib/waydroid/rootfs/vendor/waydroid.prop']
(003483) [14:30:35] % sudo chmod 777 -R /dev/ashmem
(003483) [14:30:35] run: ['sudo', 'chmod', '777', '-R', '/dev/ashmem']
(003483) [14:30:35] % sudo chmod 777 -R /dev/dri
(003483) [14:30:35] run: ['sudo', 'chmod', '777', '-R', '/dev/dri']
(003483) [14:30:35] % sudo chmod 777 -R /dev/fb0
(003483) [14:30:35] run: ['sudo', 'chmod', '777', '-R', '/dev/fb0']
(003483) [14:30:35] % sudo lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init
(003483) [14:30:35] run: ['sudo', 'lxc-start', '-P', '/var/lib/waydroid/lxc', '-F', '-n', 'waydroid', '--', '/init']
(003483) [14:30:35] New background process: pid=3563, output=background
lxc-start: waydroid: network.c: netdev_configure_server_veth: 708 No such file or directory - Failed to attach "vethhkqo7M" to bridge "waydroid0", bridge interface doesn't exist
lxc-start: waydroid: network.c: lxc_create_network_priv: 3419 No such file or directory - Failed to create network device
lxc-start: waydroid: start.c: lxc_spawn: 1826 Failed to create the network
lxc-start: waydroid: start.c: __lxc_start: 2053 Failed to spawn container "waydroid"
lxc-start: waydroid: conf.c: run_buffer: 323 Script exited with status 126
lxc-start: waydroid: start.c: lxc_end: 996 Failed to run lxc.hook.post-stop for container "waydroid"
lxc-start: waydroid: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: waydroid: tools/lxc_start.c: main: 313 Additional information can be obtained by setting the --logfile and --logpriority options
(003483) [14:30:36] waiting 10 seconds for container to start...
(003483) [14:30:37] waiting 9 seconds for container to start...
(003483) [14:30:38] waiting 8 seconds for container to start...
(003483) [14:30:39] waiting 7 seconds for container to start...
(003483) [14:30:40] waiting 6 seconds for container to start...
(003483) [14:30:41] waiting 5 seconds for container to start...
(003483) [14:30:42] waiting 4 seconds for container to start...
(003483) [14:30:43] waiting 3 seconds for container to start...
(003483) [14:30:44] waiting 2 seconds for container to start...
(003608) [14:30:44] WayDroid container is STOPPED
(003483) [14:30:45] waiting 1 seconds for container to start...
(003483) [14:30:46] ERROR: container failed to start
(003483) [14:30:46] See also: <https://github.com/waydroid>

On gnome40 wayland, if relevant.

Waydroid will not start without the binder and ashmem kernel modules. This has to be notified to the user.

On Linux Zen those modules are present and they can be loaded, however only recent versions of Waydroid support it; therefore, please always use upstream Git until the WayDroid devs do tagged releases.

some notes:
1. log of android container can be found at journalctl
2. init may failed to start lkmd, add psi=1 to kernel parameter to resolve this.