Browse code
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 <github@gone.nl>
Sebastiaan van Stijn authored on 2016/02/18 07:45:18Showing 1 changed files
| ... | ... |
@@ -19,9 +19,11 @@ feature to restrict your application's access. |
| 19 | 19 |
This feature is available only if the kernel is configured with `CONFIG_SECCOMP` |
| 20 | 20 |
enabled. |
| 21 | 21 |
|
| 22 |
-> **Note**: On Ubuntu 14.04, Debian Wheezy, and Debian Jessie, you must download |
|
| 23 |
-> the [latest static Docker Linux binary](../installation/binaries.md) to use |
|
| 24 |
-> seccomp. |
|
| 22 |
+> **Note**: Seccomp profiles require seccomp 2.2.1 and are only |
|
| 23 |
+> available starting with Debian 9 "Stretch", Ubuntu 15.10 "Wily", and |
|
| 24 |
+> Fedora 22. To use this feature on Ubuntu 14.04, Debian Wheezy, or |
|
| 25 |
+> Debian Jessie, you must download the [latest static Docker Linux binary](../installation/binaries.md). |
|
| 26 |
+> This feature is currently *not* available on other distributions. |
|
| 25 | 27 |
|
| 26 | 28 |
## Passing a profile for a container |
| 27 | 29 |
|