ryantimwilson / rpms / systemd

Forked from rpms/systemd a month ago
Clone
ff6046
From e8ead61e1c0a919a97df64b14dbd572ef7c830d2 Mon Sep 17 00:00:00 2001
ff6046
From: Frantisek Sumsal <frantisek@sumsal.cz>
ff6046
Date: Sat, 15 Dec 2018 20:22:31 +0100
ff6046
Subject: [PATCH] tests: explicitly enable user namespaces for
ff6046
 TEST-13-NSPAWN-SMOKE
ff6046
ff6046
Cherry-picked from: 67f5c0c776ce9449ad21e9854665573a05141fd4
ff6046
---
ff6046
 test/TEST-13-NSPAWN-SMOKE/test.sh | 7 ++++++-
ff6046
 1 file changed, 6 insertions(+), 1 deletion(-)
ff6046
ff6046
diff --git a/test/TEST-13-NSPAWN-SMOKE/test.sh b/test/TEST-13-NSPAWN-SMOKE/test.sh
ff6046
index 6a0cb42eaf..c0789b5d20 100755
ff6046
--- a/test/TEST-13-NSPAWN-SMOKE/test.sh
ff6046
+++ b/test/TEST-13-NSPAWN-SMOKE/test.sh
ff6046
@@ -18,7 +18,7 @@ test_setup() {
ff6046
         eval $(udevadm info --export --query=env --name=${LOOPDEV}p2)
ff6046
 
ff6046
         setup_basic_environment
ff6046
-        dracut_install busybox chmod rmdir unshare ip
ff6046
+        dracut_install busybox chmod rmdir unshare ip sysctl
ff6046
 
ff6046
         cp create-busybox-container $initdir/
ff6046
 
ff6046
@@ -63,6 +63,11 @@ if [[ -f /proc/1/ns/cgroup ]]; then
ff6046
 fi
ff6046
 
ff6046
 is_user_ns_supported=no
ff6046
+# On some systems (e.g. CentOS 7) the default limit for user namespaces
ff6046
+# is set to 0, which causes the following unshare syscall to fail, even
ff6046
+# with enabled user namespaces support. By setting this value explicitly
ff6046
+# we can ensure the user namespaces support to be detected correctly.
ff6046
+sysctl -w user.max_user_namespaces=10000
ff6046
 if unshare -U sh -c :; then
ff6046
     is_user_ns_supported=yes
ff6046
 fi