From ba9125a4e731432323d93e2119f3596baee75c2f Mon Sep 17 00:00:00 2001 From: Jessica Frazelle Date: Tue, 29 Dec 2015 11:21:33 -0800 Subject: [PATCH] remove seccomp from seccomp profile This can be allowed because it should only restrict more per the seccomp docs, and multiple apps use it today. Signed-off-by: Jessica Frazelle Upstream-commit: b610fc226afdf663b0ad46ad982c27fdee61f671 Component: engine --- .../engine/daemon/execdriver/native/seccomp_default.go | 6 ------ 1 file changed, 6 deletions(-) diff --git a/components/engine/daemon/execdriver/native/seccomp_default.go b/components/engine/daemon/execdriver/native/seccomp_default.go index 94a8efbb63..858db11053 100644 --- a/components/engine/daemon/execdriver/native/seccomp_default.go +++ b/components/engine/daemon/execdriver/native/seccomp_default.go @@ -254,12 +254,6 @@ var defaultSeccompProfile = &configs.Seccomp{ Action: configs.Errno, Args: []*configs.Arg{}, }, - { - // meta, deny seccomp - Name: "seccomp", - Action: configs.Errno, - Args: []*configs.Arg{}, - }, { // Terrifying syscalls that modify kernel memory and NUMA settings. // They're gated by CAP_SYS_NICE,