Open rakesh8081 opened 5 years ago
Does the centos machine support user namespaces? Is this possibly the same issue: https://github.com/lethalman/nix-user-chroot/issues/9 (nix-bundle uses nix-user-chroot)
I believe it does. But clearly the kernel version is not >3.x. Some outputs for more reference.
[root@ip-172-30-14-129 ~]#
[root@ip-172-30-14-129 ~]#
[root@ip-172-30-14-129 ~]# uname -a
Linux ip-172-30-14-129 2.6.32-431.11.2.el6.x86_64 #1 SMP Tue Mar 25 19:59:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[root@ip-172-30-14-129 ~]# grep CONFIG_USER_NS /boot/config-$(uname -r)
CONFIG_USER_NS=y
[root@ip-172-30-14-129 ~]# echo $0
-bash
[root@ip-172-30-14-129 ~]# if [[ `sudo cat /boot/config-$(uname -a | awk '{print $3}') |grep '^CONFIG_USER_NS'` == "CONFIG_USER_NS=y" ]]; then echo "You have support for User Namespaces"; else echo "Sorry, you don't have support for User Namespaces"; fi
You have support for User Namespaces
[root@ip-172-30-14-129 ~]#
[root@ip-172-30-14-129 ~]# unshare
Usage: unshare [options] <program> [args...]
Run program with some namespaces unshared from parent
-h, --help usage information (this)
-m, --mount unshare mounts namespace
-u, --uts unshare UTS namespace (hostname etc)
-i, --ipc unshare System V IPC namespace
-n, --net unshare network namespace
For more information see unshare(1).
[root@ip-172-30-14-129 ~]#
Can you check what the other setting mentioned in that bug is (assuming it exists on your system)
cat /proc/sys/user/max_user_namespaces
The file don’t exist in system.
[root@ip-172-30-14-129 ~]# cat /proc/sys/user/max_user_namespaces
cat: /proc/sys/user/max_user_namespaces: No such file or directory
[root@ip-172-30-14-129 ~]#
[root@ip-172-30-14-129 ~]# locate max_user_namespace
[root@ip-172-30-14-129 ~]#
I bundled firefox which started up in Manjaro/Arch but cannot display any online page. internal stuff like browsing history works tho.
I am trying to build latest possible curl version using nix-bundle for centos 6.5. The build was done on a Ubuntu 18.0 VM running on Windows. It works pretty fine where it was build, here are the outputs
however when I use the same binary in a Centos machine running on aws, it doesn't work. The outputs on Centos is as below:
so the question is what exactly went wrong. Please let me know for any additional logs.