Project information: Waydroid is a container-based approach to boot a full Android system on a regular GNU/Linux system
Name: Waydroid
Homepage: documentation , source code
License: GNU General Public License v3.0
Upstream has been contacted: Yes, here .
7 Likes
Since it seems to use LXC under the hood, I don’t think it’s possible to run it in flatpak sandbox.
Yeah, the current dependency on LXC is a big blocker. Someone who is familiar with Waydroid would need to evaluate if it’s feasible to move to Flatpak sub sandboxes for Flatpak builds. I don’t know what features of LXC they depend on, and how possible it is to use those features in Flatpak sub sandboxes.
See also https://github.com/flatpak/xdg-desktop-portal/issues/637#issuecomment-956498729
1 Like
evaluate if it’s feasible to move to Flatpak sub sandboxes
This is unlikely to be possible either. Running an Android system container means you need at least multiple UIDs inside the container, which Flatpak (sub)sandbox doesn’t provide.
Yajo
January 21, 2022, 5:02am
5
The title says waydroid but the links are for anbox, these are different projects AFAIK.
3 Likes
realgrm
January 21, 2022, 12:42pm
6
Thanks. Updated and opened a request for Anbox .
I probably open the 2 projects at the same time and made a little confusion while writing.
4 Likes
Did you mean to put
opened 03:53PM - 22 Sep 21 UTC
closed 12:55PM - 19 Nov 22 UTC
https://www.flatpak.org/
This would make it hopefully easier to install on non … Debian-based distros.
Since Flatpak is a container based system, I'm not sure how easy this is given Waydroid is itself a container.
there instead? I don’t see the relevance of
opened 06:26AM - 21 Sep 21 UTC
closed 03:57PM - 26 Mar 22 UTC
WayDroid does not start. Here are some relevent data,
`sudo waydroid init`
```…
[11:52:15] Already initialized
```
`sudo systemctl status waydroid-container.service`
```
● waydroid-container.service - Waydroid Container
Loaded: loaded (/lib/systemd/system/waydroid-container.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-09-21 11:51:36 IST; 2min 13s ago
Process: 4500 ExecStart=/usr/bin/waydroid container start (code=exited, status=0/SUCCESS)
Process: 4503 ExecStop=/usr/bin/waydroid container stop (code=exited, status=1/FAILURE)
Process: 4510 ExecStopPost=/usr/bin/waydroid session stop (code=exited, status=0/SUCCESS)
Main PID: 4500 (code=exited, status=0/SUCCESS)
CPU: 395ms
Sep 21 11:51:36 missu-aspiree5571 sudo[4508]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/lxc-stop -P /var/lib/waydroid/lxc -n waydroid -k
Sep 21 11:51:36 missu-aspiree5571 sudo[4508]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Sep 21 11:51:36 missu-aspiree5571 sudo[4508]: pam_unix(sudo:session): session closed for user root
Sep 21 11:51:36 missu-aspiree5571 waydroid[4503]: [11:51:36] NOTE: The failed command's output is above the ^^^ line in the log file: /var/lib/waydroid/waydroid.log
Sep 21 11:51:36 missu-aspiree5571 waydroid[4503]: [11:51:36] ERROR: Command failed: % sudo lxc-stop -P /var/lib/waydroid/lxc -n waydroid -k
Sep 21 11:51:36 missu-aspiree5571 waydroid[4503]: [11:51:36] See also: <https://github.com/waydroid>
Sep 21 11:51:36 missu-aspiree5571 waydroid[4503]: Run 'waydroid log' for details.
Sep 21 11:51:36 missu-aspiree5571 systemd[1]: waydroid-container.service: Control process exited, code=exited, status=1/FAILURE
Sep 21 11:51:36 missu-aspiree5571 waydroid[4510]: [11:51:36] WayDroid session is not started
Sep 21 11:51:36 missu-aspiree5571 systemd[1]: waydroid-container.service: Failed with result 'exit-code'.
```
`waydroid session start`
```[11:55:29] XDG Session is not "wayland"```
In another shell,
`waydroid status`
```Session: RUNNING
Container: STOPPED
Vendor type: MAINLINE
Session user: missu(1000)
Wayland display: None
```
` sudo waydroid container start`
```
waydroid doesn't exist
[11:56:00] WayDroid container is
```
Distro Debian 11
Kernel 5.14.6-xanmod1-cacule
Let me know if anything else required