chroot: can't execute '/bin/busybox': No such file or directory

Issue Summary

Description: I attempted to use pmbootstrap with the command ./pmbootstrap.py flasher --method=adb sideload in TWRP > ADB Sideload mode to flash my device. However, the process failed with the following error message:

+ chroot /tmp/postmarketos/chroot /bin/busybox --install /bin
chroot: can't execute '/bin/busybox': No such file or directory

It appears to be the same as issue #1962 (closed). But that issue was closed.

Expected Behavior: The pmbootstrap command should successfully execute and initiate the sideload process.

Steps to Reproduce

1. Boot the device into TWRP recovery mode.
2. Select ADB Sideload from the TWRP menu.
3. Execute the command ./pmbootstrap.py flasher --method=adb sideload on a connected computer.

Actual Behavior

The process fails with the error:

chroot: can't execute '/bin/busybox': No such file or directory

Additional Information

• Device: samsung-grandpplte
• pmbootstrap Version: 2.3.0

pmbootstrap log

[v20.05]
description=Old release (unsupported)
branch_pmaports=v20.05
branch_aports=3.12-stable
mirrordir_alpine=v3.12
(038534) [09:29:07] (native) calculate depends of android-tools (pmbootstrap -v for details)
(038534) [09:29:07] (native) install android-tools
(038534) [09:29:07] % doas rm -f /home/user/.local/var/pmbootstrap/chroot_native/tmp/apk_progress_fifo
(038534) [09:29:07] % doas mkfifo /home/user/.local/var/pmbootstrap/chroot_native/tmp/apk_progress_fifo
(038534) [09:29:07] (native) % cat /tmp/apk_progress_fifo
(038534) [09:29:07] (native) % sh -c exec 3>/tmp/apk_progress_fifo; apk --no-progress --progress-fd 3 add android-tools --no-interactive
(038534) [09:29:07] New background process: pid=38555, output=background
WARNING: opening /mnt/pmbootstrap/packages: No such file or directory
OK: 296 MiB in 166 packages
(038534) [09:29:08] (native) calculate depends of android-tools (pmbootstrap -v for details)
(038534) [09:29:08] (native) install android-tools
(038534) [09:29:08] % doas rm -f /home/user/.local/var/pmbootstrap/chroot_native/tmp/apk_progress_fifo
(038534) [09:29:08] % doas mkfifo /home/user/.local/var/pmbootstrap/chroot_native/tmp/apk_progress_fifo
(038534) [09:29:08] (native) % cat /tmp/apk_progress_fifo
(038534) [09:29:08] (native) % sh -c exec 3>/tmp/apk_progress_fifo; apk --no-progress --progress-fd 3 add android-tools --no-interactive
(038534) [09:29:08] New background process: pid=38589, output=background
WARNING: opening /mnt/pmbootstrap/packages: No such file or directory
OK: 296 MiB in 166 packages
(038534) [09:29:08] (native) % echo < wait for any device >
< wait for any device >
(038534) [09:29:08] (native) % adb -P 5038 wait-for-usb-sideload
* daemon not running; starting now at tcp:5038
* daemon started successfully
(038534) [09:29:14] (native) % adb -P 5038 sideload /mnt/buildroot_aarch64/var/lib/postmarketos-android-recovery-installer/pmos-samsung-grandpplte.zip
Total xfer: 0.06x                                                                                                            
(038534) [09:29:19] NOTE: chroot is still active (use 'pmbootstrap shutdown' as necessary)
(038534) [09:29:19] DONE!
(038824) [09:29:39] % tail -n 60 -F /home/user/.local/var/pmbootstrap/log.txt
(038824) [09:29:39] *** output passed to pmbootstrap stdout, not to this log ***

Hi, could you run pmbootstrap log in another terminal while running the command in question and then grab the full output? if you run it after the fact it only gets so many lines...

I suspect we're missing a chroot init somewhere

By Caleb Connolly on 2024-06-24T10:30:36

Did it. Here is my command output:

% ./pmbootstrap.py flasher --method=adb sideload
{'edge': '2.14.0-r5', 'v3.19': '2.14.0-r5', 'v3.18': '2.14.0-r2', 'v3.17': '2.12.10-r1', 'v3.16': '2.12.9-r3', 'v3.15': '2.12.7-r3', 'v3.14': '2.12.7-r0', 'v3.13': '2.12.7-r0', 'v3.12': '2.10.8-r1'}
[13:25:42] Update package index for x86_64 (3 file(s))
[13:25:44] (native) install android-tools
[13:25:46] (native) install android-tools
< wait for any device >
* daemon not running; starting now at tcp:5038
* daemon started successfully
serving: '/mnt/buildroot_aarch64/var/lib/postmarketos-android-recovery-installeserving: '/mnt/buildroot_aarch64/var/lib/postmarketos-android-recovery-installeserving: '/mnt/buildroot_aarch64/var/lib/postmarketos-android-recovery-installeTotal xfer: 0.06x                                                                                                            
[13:26:02] NOTE: chroot is still active (use 'pmbootstrap shutdown' as necessary)
[13:26:02] DONE!

I uploaded pmbootstrap log output to a paste bin service: https://justpaste.it/cq0c3

By FurkanMuslu on 2024-06-24T10:30:36