Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
just-a-pony opened this issue Jan 29, 2023 · 11 comments
Labels
bug Something isn't working

Comments

@just-a-pony
Copy link

Describe the bug
A clear and concise description of what the bug is.

systemctl start waydroid-container.service

sudo waydroid_magisk.py install

[16:51:41] - INFO - Downloading Magisk Delta: canary-80855189-delta
[16:51:42] - INFO - Extracting Magisk Delta
[16:51:42] - INFO - Installing Magisk Delta
[16:51:42] - INFO - Backing up bootanim.rc
[16:51:42] - INFO - Patching bootanim.rc
[16:51:42] - INFO - Finishing installation
[16:51:42] - INFO - Done
[16:51:42] - INFO - Run waydroid_magisk setup after waydroid starts again or install Magisk Delta Manager

waydroid show-full-ui
sudo waydroid_magisk.py setup

[16:53:08] - ERROR - Magisk Delta is not installed
[16:53:08] - ERROR - Magisk Delta is not installed
[16:53:08] - ERROR - Magisk Delta is not installed
[16:53:08] - ERROR - Magisk Delta is not installed
[16:53:08] - ERROR - Magisk Delta is not installed
[16:53:08] - ERROR - Magisk Delta is not installed
[16:53:08] - INFO - Stopping Waydroid in 5 (press ^C to cancel)
[16:53:09] - INFO - Stopping Waydroid in 4 (press ^C to cancel)
[16:53:10] - INFO - Stopping Waydroid in 3 (press ^C to cancel)
[16:53:11] - INFO - Stopping Waydroid in 2 (press ^C to cancel)
[16:53:12] - INFO - Stopping Waydroid in 1 (press ^C to cancel)
[16:53: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"
[16:53:13] - INFO - Starting Waydroid

Now,if i install nagisk delta manually from apk in the waydroid,it will show
图片
If i ckick "ok", "dirct install into system partition",
图片
if i ctrl+c waydroid show-full-ui ,and rerun sudo waydroid_magisk.py install,

[17:04:43] - ERROR - Magisk Delta already installed!

Logs
From sudo waydroid_magisk log --save
No,it will show [17:04:14] - ERROR - Magisk Delta is not installed
Desktop (please complete the following information):

  • OS: [e.g. iOS] Arch Linux with linux-xanmod-anbox
  • Waydroid Version: [e.g. 1.4.0] 1.3.4

Additional context
Add any other context about the problem here.

@just-a-pony just-a-pony added the bug Something isn't working label Jan 29, 2023
@nitanmarcel
Copy link
Owner

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
Copy link
Owner

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
Copy link
Owner

nitanmarcel commented Jan 29, 2023

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
Copy link
Author

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
Copy link
Owner

nitanmarcel commented Jan 29, 2023

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

@nitanmarcel
Copy link
Owner

Actually @just-a-pony in sudo waydroid shell can you do which service and send me the output?

Thanks

@just-a-pony
Copy link
Author

just-a-pony commented Jan 29, 2023

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
Copy link
Author

just-a-pony commented Jan 29, 2023

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
Copy link
Owner

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
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants