Bug 1361671

Summary: [RFE] Provide support docker seccomp profiles for OpenShift applications
Product: OpenShift Container Platform Reporter: Ryan Howe <rhowe>
Component: RFEAssignee: Paul Weil <pweil>
Status: CLOSED ERRATA QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.1CC: aos-bugs, erich, jokerman, mmccomas, tdawson, wmeng
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1379761 (view as bug list) Environment:
Last Closed: 2016-09-27 09:42:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1379761    

Description Ryan Howe 2016-07-29 17:13:17 UTC 
1. Proposed title of this feature request
2. Who is the customer behind the request?

Account name: (Acct. # 5646191

SRM customer: ?

TAM customer: ?

Strategic Customer: yes

3. What is the nature and description of the request?

 OpenShift to support docker seccomp profiles. 

https://trello.com/c/j5alQzVy/646-3-downstream-support-for-seccomp-profiles
https://github.com/kubernetes/kubernetes/issues/20870
https://github.com/docker/docker/blob/master/docs/security/seccomp.md

4. Why does the customer need this? (List the business requirements here)

  Ability to have better control over the syscall a container can make. 

5. How would the customer like to achieve this? (List the functional requirements here)
  
  Configure the profile via Security Context Constraint
Comment 2 errata-xmlrpc 2016-09-27 09:42:04 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1933