Skip to content

Add AUDIT_WRITE cap#7179

Merged
crosbymichael merged 1 commit intomoby:masterfrom
LK4D4:add_cap_audit_write_#6345
Jul 24, 2014
Merged

Add AUDIT_WRITE cap#7179
crosbymichael merged 1 commit intomoby:masterfrom
LK4D4:add_cap_audit_write_#6345

Conversation

@LK4D4
Copy link
Copy Markdown
Contributor

@LK4D4 LK4D4 commented Jul 23, 2014

Fixes #6345

Thanks @larsks for outstanding investigation

Fixes #6345

Thanks @larsks for outstanding investigation

Docker-DCO-1.1-Signed-off-by: Alexandr Morozov <[email protected]> (github: LK4D4)
@LK4D4
Copy link
Copy Markdown
Contributor Author

LK4D4 commented Jul 23, 2014

ping @crosbymichael @unclejack

@thaJeztah thaJeztah mentioned this pull request Jul 23, 2014
@rhatdan
Copy link
Copy Markdown
Contributor

rhatdan commented Jul 23, 2014

Yes I guess we need this, although I would really prefer not to get audit messages from the container. There is an effort to add namespace to the audit subsystem which should be able to eliminate this need or at least stop audit messages from showing up in the hosts audit log.

@crosbymichael
Copy link
Copy Markdown
Contributor

@larsks spoke with some of the audit developers and they suggested that we retain AUDIT_WRITE to solve the issues that we are seeing on the newer kernel releases.

@unclejack
Copy link
Copy Markdown
Contributor

tested with kernel 3.14.12 and kernel 3.15.6

LGTM

@rhatdan
Copy link
Copy Markdown
Contributor

rhatdan commented Jul 24, 2014

LGTM. I have a patch with AUDIT_WRITE added back in for our testers.

@crosbymichael
Copy link
Copy Markdown
Contributor

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docker containers can conflict with users on host system in Linux 3.15

4 participants