I have Waydroid working on what (last time I checked was yesterday) is the latest version of whonix on KVM this is because Anbox sadly did not work. I have also managed to get some APKs on there and they work.
While this is all good, I am experiencing some issues, namely that the waydroid setup I have going right now does not seem to be connected to the internet, which I require for the task I am doing, as it requires a connection. I suspect that this could be related to the firewall in whonix, as I saw in a past question about waydroid where the user solved their problem by allowing UDP (I think), and it was for a network related issue. I completed the steps in the wiki and nothing seems to have changed.
Anybody else using waydroid on whonix waydroid with this problem? Also if anyone answering wants more details about my problem feel free to HMU
Not as long as this notice is on top of that wiki page:
Documentation for this is incomplete. Contributions are happily considered! See this for potential alternatives.
Documenting installation of Waydroid including digital software verification was the simple part. But apparently Waydroid only runs with Wayland which is more difficult to install, specifically in Qubes.
There were problems after setting waydroid to whonix 22.214.171.124 for kvm in the same way that the author of this topic indicated in the first post. Namely, there is no Internet inside the container itself. At the same time, both on whonix 16x and on pure debian 12 bookworm (connected to whonix gateway), everything works without problems. True, on the old and stable version of whonix, I had to completely deactivate the firewall, because disabling udp only allowed running waydroid, but not accessing the Internet through it. But in whonix 17 this was not enough and when trying to go online, it writes something like: “unable to resolve host” in all applications (browser, f-droid and a few more accidentally installed). Searching on the github in the waydroid branch for tags like “unable to resolve host”, etc., nothing was found. Yes, and everything works on debian 12 and whonix 16, so I dare to assume that the problem is in whonix 17, but specifically what, I have no idea …
Experimentally, I found out that the problem was in apparmor profile dnsmasq. Only by completely disabling it did the network fully work on waydroid and the applications in it. I checked whonix 17 on virtualbox more and there this apparmor profile does not affect the performance of the network. It is strange that on kvm the situation is reversed. Again, I will make a reservation, apparmor profile dnsmasq in any case needs to be edited by adding:
but it is applicable to all OS. On whonix 16 kvm it was done and everything functioned perfectly, but on whonix 17 kvm for some reason it didn’t.
I understand it. I’m just a little surprised that in the last whonix 16 (although still relevant at the moment, before the official release of version 17) in all editions, the activated profile dnsmasq does not break anything, in whonix 17 virtualbox everything is also surprisingly good, but not in kvm 17.
Apparently these are some features of the network, unique to the internal operation of virtual machines kvm and the transition to debian bookworm, but I don’t understand anything about this)