lxc-attach: waydroid: ../src/lxc/attach.c: lxc_attach_run_command: 1841 No such file or directory - Failed to exec "service"

[nitanmarcel]

lxc-attach: waydroid: ../src/lxc/attach.c: lxc_attach_run_command: 1841 No such file or directory - Failed to exec "service"

[nitanmarcel]

Ignore that. I should probably silence it. Or probably see why it's broken on some distros.

Anyway, closing this issue :) glad we got it working

[Just-A-Pony]

https://drive.google.com/file/d/1IzjPT9Q9XrGycC-C3ow-NaUHjLmccexG/view?usp=sharing
https://drive.google.com/file/d/1SZHD8O-q3gPvn4JNIT11H19bG2jfSgca/view?usp=sharing
/usr/share/waydroid-extra/images/

[nitanmarcel]

Are the images used clean? Meaning no other modifications applied to it.

Also a cleanup with rm -rf /var/lib/waydroid and sudo waydroid init should probably fix it, as it seems something went wrong when installing Magisk

[nitanmarcel]

Oh sorry.

The last two commits should fix it. Instead of cleaning the images you can do (after updating waydroid-magisk)

sudo waydroid_magisk remove

Then start everything based by the instructions.

[nitanmarcel]

And about the Magisk Delta Manager error. I've moved the FAQ related to it from the Ubuntu Touch section to a section of it's own.

https://github.com/nitanmarcel/waydroid-magisk#magisk-delta-fails-to-patch-selinux-policy (Note that you can still use Magisk Delta Manager, but just don't update, do the additional setup from the manager"

[Just-A-Pony]

Oh sorry.

The last two commits should fix it. Instead of cleaning the images you can do (after updating waydroid-magisk)

sudo waydroid_magisk remove

Then start everything based by the instructions.

Thanks! it works!

[21:19:59] - INFO - Daemon: Running
[21:19:59] - INFO - Magisk Version: 80855189-delta:MAGISKSU

But there's still a lxc-attach: waydroid: ../src/lxc/attach.c: lxc_attach_run_command: 1841 No such file or directory - Failed to exec "service" during the waydroid_magisk.py setup

[21:19:08] - INFO - Stopping Waydroid in 5 (press ^C to cancel)
[21:19:09] - INFO - Stopping Waydroid in 4 (press ^C to cancel)
[21:19:10] - INFO - Stopping Waydroid in 3 (press ^C to cancel)
[21:19:11] - INFO - Stopping Waydroid in 2 (press ^C to cancel)
[21:19:12] - INFO - Stopping Waydroid in 1 (press ^C to cancel)
[21:19:13] - INFO - Stopping waydroid
lxc-attach: waydroid: ../src/lxc/attach.c: lxc_attach_run_command: 1841 No such file or directory - Failed to exec "service"
[21:19:13] - INFO - Starting Waydroid

[nitanmarcel]

Actually @Just-A-Pony in sudo waydroid shell can you do which service and send me the output?

Thanks

[Just-A-Pony]

Actually @Just-A-Pony in sudo waydroid shell can you do which service and send me the output?

Thanks

/system/bin/service
And if I run service call waydroidhardware 4manually in the waydroid,It seams work properly which restart the waydroid

[Just-A-Pony]

I found this in archwiki :

5.3 Error: unknown command
The error may happen when a basic command (ls, cat, etc.) on an attached container is typed hen a different Linux distribution is containerized relative to the host system (e.g. Debian container in Arch Linux host system). Upon attaching, use the argument --clear-env:
lxc-attach -n container_name --clear-env

[nitanmarcel]

I found this in archwiki :

5.3 Error: unknown command
The error may happen when a basic command (ls, cat, etc.) on an attached container is typed hen a different Linux distribution is containerized relative to the host system (e.g. Debian container in Arch Linux host system). Upon attaching, use the argument --clear-env:
lxc-attach -n container_name --clear-env

Oh. My bad there. It seems I forgot to pass the env argument in subprocess.run

[nitanmarcel]

I found this in archwiki :

5.3 Error: unknown command
The error may happen when a basic command (ls, cat, etc.) on an attached container is typed hen a different Linux distribution is containerized relative to the host system (e.g. Debian container in Arch Linux host system). Upon attaching, use the argument --clear-env:
lxc-attach -n container_name --clear-env

this should be also fixed now