Closed nathaneltitane closed 3 months ago
calling any utility that resides under $PREFIX/bin ends in '...: cannot execute: required file not found'
Try to use strace -f
to find which file is not found.
calling any utility that resides under $PREFIX/bin ends in '...: cannot execute: required file not found'
Try to use
strace -f
to find which file is not found.
EDIT: as stated above, any attempt at accessing any file under $PREFIX/bin results in that error - the binds are functional and BASH autocomplete does find the references: ex. typing termu..[TAB] does give all termux-* utils.
Problem description
Apologies in advance if this indeed an issue with my scripted routine
Cannot run any bound directory script,binary or utility through proot from container (Debian 12) - any attempt at calling any utility that resides under $PREFIX/bin ends in '...: cannot execute: required file not found' I have stripped my container-session script to hardcoded defaults to remove any possibility of it being the script and i still get the same issue.
This problem was not present a couple of months ago - matter of fact, I implemented termux-x11/virgl rendering in full into 'container-session' around late may 2024 / beginning june 2024 and it was running just fine.
Ref.: https://github.com/nathaneltitane/dextop
'container-session' : https://github.com/nathaneltitane/dextop/blob/main/container-session
Steps to reproduce
run session-basic script enter session attempt running any binary/script/utility that resides under $PREFIX/bin (ex.: termux-x11)
session-basic = stripped down version of container-session (script is in tar)
session-basic.tar.gz
Expected behavior
Running termux-x11 steps to a graphical interface or accessing any script, utility or binary from the 'termux side' of the install ($PREFIX/bin) should run normally and without rror as long as all requirements are fulfilled (architecture, libraries, etc)
Additional information
Normal behavior of a session when dextop is installed and running normally (Termux side, no proot or container)
https://github.com/user-attachments/assets/81b214bf-893c-4120-b53b-91df4e9153c3
Termux setup (green prompt runs perfectly fine, as expected)
Accessing the container side (red/fuschia prompt) results:
https://github.com/user-attachments/assets/505212ae-877e-4127-b333-4d0cc13f4114
Expected: container session should normally trigger the virgl server and termux-x11 the same way that it does on the termux side.