From b800719b7b5dac5ba2cbd57825491cd192b98635 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Wed, 17 Feb 2016 23:45:18 +0100 Subject: [PATCH] Be more explicit on seccomp availability Seccomp is only *compiled* in binaries built for distros that ship with seccomp 2.2.1 or higher, and in the static binaries. The static binaries are not really useful for RHEL and CentOS, because devicemapper does not work properly with the static binaries, so static binaries is only an option for Ubuntu and Debian. Signed-off-by: Sebastiaan van Stijn Upstream-commit: 13839a6d328692c672394811ee3afd9a168fc328 Component: engine --- components/engine/docs/security/seccomp.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/components/engine/docs/security/seccomp.md b/components/engine/docs/security/seccomp.md index 5bfed0f647..dbaf4d1d2a 100644 --- a/components/engine/docs/security/seccomp.md +++ b/components/engine/docs/security/seccomp.md @@ -19,9 +19,11 @@ feature to restrict your application's access. This feature is available only if the kernel is configured with `CONFIG_SECCOMP` enabled. -> **Note**: On Ubuntu 14.04, Debian Wheezy, and Debian Jessie, you must download -> the [latest static Docker Linux binary](../installation/binaries.md) to use -> seccomp. +> **Note**: Seccomp profiles require seccomp 2.2.1 and are only +> available starting with Debian 9 "Stretch", Ubuntu 15.10 "Wily", and +> Fedora 22. To use this feature on Ubuntu 14.04, Debian Wheezy, or +> Debian Jessie, you must download the [latest static Docker Linux binary](../installation/binaries.md). +> This feature is currently *not* available on other distributions. ## Passing a profile for a container