FATAL: kernel too old (kernel_version: 3.10)

[hash-ir]

Hi,

I was trying to run junest on a cluster where I don't have root access. I get the following errors while doing so:

$ junest
FATAL: kernel too old
Error: Something went wrong while executing bwrap command. Exiting

$ junest proot
proot warning: can't chdir("/ssdscratch/neuroglancer/./.") in the guest rootfs: No such file or directory
proot info: default working directory is now "/"
proot info: pid 15923: terminated with signal 11
proot warning: can't chdir("/ssdscratch/neuroglancer/./.") in the guest rootfs: No such file or directory
proot info: default working directory is now "/"
FATAL: kernel too old
Error: Something went wrong with proot command. Exiting

Here are the system details:

$ bash --version
GNU bash, version 4.2.46(2)-release (x86_64-redhat-linux-gnu)

$ uname -r
3.10.0-1160.11.1.el7.x86_64

$ lsb_release -a
LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	CentOS
Description:	CentOS Linux release 7.9.2009 (Core)
Release:	7.9.2009
Codename:	Core

What could be the issue here?

Best regards,
Hashir

[Mencu]

Hi,

I have the same problem. Also, the troubleshooting section didn't help. I still get the same error.

Best,
Andrei Mancu

[midnightexigent]

same problem here

$ uname -r
3.10.0-1160.25.1.el7.x86_64

$ junest proot -b "-k 3.10 --verbose=1"
...
proot info: default working directory is now "/"
proot info: glue rootfs = /tmp/proot-59793-5mJfSq
proot info: exe = /usr/bin/sh
proot info: argv = /bin/sh --login -c :
proot info: initial cwd = /
proot info: verbose level = 1
proot info: pid 59793: access to "/dev/pts/0" (fd 0) won't be translated until closed
proot info: pid 59793: access to "/dev/pts/0" (fd 1) won't be translated until closed
proot info: pid 59793: access to "/dev/pts/0" (fd 2) won't be translated until closed
proot info: pid 59793: access to "/proc/59793/fd" (fd 3) won't be translated until closed
FATAL: kernel too old
proot info: pid 59797: exited with status 127
Error: Something went wrong with proot command. Exiting

[ductri]

I got the same issue on CentOS

[jschwartzenberg]

I think Arch is simply moving too fast for RHEL6/RHEL7 host environment nowadays. Maybe it makes sense to use something slightly less bleeding edge instead? What about Debian Stable or Ubuntu LTS?

[SnwMds]

Found this workaround for proot:

$ mv ${HOME}/.junest/bin/proot-x86_64 ${HOME}/.junest/bin/proot
$ echo "#\!/bin/bash\n\n${HOME}/.junest/usr/bin/proot --kernel-release=5.16 \${@}" > ${HOME}/.junest/bin/proot-x86_64
$ chmod 500 ${HOME}/.junest/bin/proot-x86_64
$ 
$ junest proot
Warn: Proot is not properly working. Disabling SECCOMP and expect the application to run slowly in particular when it uses syscalls intensively.
Try to use Linux namespace instead as it is more reliable: junest ns
[snwmds@localhost ~]$

Not sure on how to make it work with ns.