On setups where waydroid container is started manually (or automatically, but without systemd service being active), script misbehaves - it ignores stuff like overlay, resizing system.img and vendor.img with every install run (so, every run, it add 500 MB to size, ad infinitum). It also result in borked installs, obviously.
It does not matter if the container is running at the time of the issue manifesting itself - it only matters if the service (which just calls /usr/bin/python3 /usr/bin/waydroid -w container start and some dnsmasq stuff, so shouldn't be that critical for waydroid_script) functionality) is running since boot.
Where possible, workaround is to temporary enable the service, and run waydroid_script after a reboot/relogin (for some reason, it doesn't grab the service being running at runtime). After the work with waydroid_script is one, service can be safely masked, again.
Obviously, it is not possible on setups without systemd.
On setups where waydroid container is started manually (or automatically, but without systemd service being active), script misbehaves - it ignores stuff like overlay, resizing system.img and vendor.img with every install run (so, every run, it add 500 MB to size, ad infinitum). It also result in borked installs, obviously.
It does not matter if the container is running at the time of the issue manifesting itself - it only matters if the service (which just calls
/usr/bin/python3 /usr/bin/waydroid -w container startand some dnsmasq stuff, so shouldn't be that critical for waydroid_script) functionality) is running since boot.Where possible, workaround is to temporary enable the service, and run waydroid_script after a reboot/relogin (for some reason, it doesn't grab the service being running at runtime). After the work with waydroid_script is one, service can be safely masked, again.
Obviously, it is not possible on setups without systemd.