Skip to content

waydroid #182

@elquike

Description

@elquike

Hi

First: I want to thank Travier and all the other contributors for the impressive work you have done.

I wanted to contribute myself also: I've tried to create a sysext for waydroid in fedora 42 silverblue with the following code:

Containerfile

FROM baseimage

RUN <<EORUN
set -xeuo pipefail
dnf install -y dnf5-plugins
dnf install -y \
    waydroid
dnf clean all
EORUN

justfile

name := "waydroid"
packages := "
waydroid
"
version_package := "waydroid"
base_images := "
quay.io/fedora-ostree-desktops/base-atomic:42 x86_64,aarch64
"

import '../sysext.just'

all: default

and inside a toolbox (fedora 42):
just build "quay.io/fedora-ostree-desktops/base-atomic:42"

which has given me a waydroid-1.5.4-1.fc42-42-x86-64.raw (5.1MB) file

Then:
sudo cp waydroid-1.5.4-1.fc42-42-x86-64.raw /var/lib/extensions.d/
sudo ln -s /var/lib/extensions.d/waydroid-1.5.4-1.fc42-42-x86-64.raw /var/lib/extensions/waydroid.raw
sudo systemctl restart systemd-sysext.service

and finally to check it has been "activaded":
systemd-sysext status

Due to an issue with dbus (waydroid/waydroid#681) I had to add the file:
/etc/dbus-1/system.d/waydroid.conf

<busconfig>
  <policy context="default">
    <allow own="id.waydro.Container"/>
    <allow send_destination="id.waydro.Container" send_interface="*"/>
  </policy>
</busconfig>

and then:
dbus-send --session --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ReloadConfig

I was able to init waydroid with
sudo waydroid init --system_channel https://ota.waydro.id/system --vendor_channel https://ota.waydro.id/vendor --system_type GAPPS

and finally
sudo waydroid container start

however this is where this go south

after checking /var/lib/waydroid/waydroid.log

I have problems with the command:
mount -o context="system_u:object_r:waydroid_rootfs_t:s0",ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs

I have tried thea above command with sudo and with another directory with it fails
sudo mount -o context="system_u:object_r:waydroid_rootfs_t:s0",ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs

mount: /var/lib/waydroid/rootfs: wrong fs type, bad option, bad superblock on /dev/loop8, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.

And this is a far as I was able to get. I'm not quite sure with the error means and my google fu has only taken me so far.

Maybe someone with more capabilites will pick up from here and solve the remaining issues

Regards

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions