nsjail can't execute dynamically-linked 32-bit binary while chroot about nsjail HOT 5 CLOSED

Hi, running dynamically linked x86 binary works fine for me using with your nsjail commandline.
My guess is that 32-bit ELF interpreter or one of its dependencies is not in one of the mounted paths.
You can get the interpreter path by running

$ file test_x86

from nsjail.

hi @happyCoder92 ,

Using file to find the interpreter location, and below is what it outputs:

test_x86: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=7f29c9f9f33886f07d6b6dbe0841c5e788639c50, not stripped

The interpreter is located at /lib/ld-linux.so.2, however, I've already included the mount point using this -R /lib argument.

Surprisingly, when I tried to run nsjail inside my Ubuntu server, it works flawlessly. This problem only occurs when I'm using Arch Linux (tried both from official Arch package and compiling from Github repo) and it still show the error.

Furthermore, I tried also to use -R / mount point (in case of I missed something). But the same error still appears.

from nsjail.

It might be that /lib/ld-linux.so.2 is a symlink on your Arch box, check where it points to.
With -R / you also have to change /test_x86 to /home/shahril/Desktop/nsjail-report/RELEASE/test_x86.

from nsjail.

Please re-open if you'd like some more suggestions

from nsjail.

I experienced this problem. The cause was amusingly and annoyingly trivial. It's because -R /lib64/ is on the command line but that path likely doesn't exist on a 32-bit system. If I remove -R /lib64/ then everything works correctly.

from nsjail.