Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds details about new non-blocking logging mode #1482

Merged
merged 1 commit into from
Feb 3, 2017

Conversation

cpuguy83
Copy link
Contributor

@cpuguy83 cpuguy83 commented Feb 2, 2017

This functionality was added in moby/moby#28762.
It allows a user to specify what to do in cases when a log message can't
be sent, block the container's stdio or drop messages.

Also removes an erroneous entry about a nats log driver, which does
not exist.

This functionality was added in moby/moby#28762.
It allows a user to specify what to do in cases when a log message can't
be sent, block the container's stdio or drop messages.

Also removes an erronious entry about a `nats` log driver, which does
not exist.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
@cpuguy83
Copy link
Contributor Author

cpuguy83 commented Feb 2, 2017

ping @thaJeztah

@mdlinville
Copy link

LGTM pending tech review. Where in the world did the nats driver content come from??

@cpuguy83
Copy link
Contributor Author

cpuguy83 commented Feb 2, 2017

Not sure but it looks like it got cherry-picked in somehow in #1187

@mdlinville
Copy link

The NATS stuff was added in #369. Should I just revert that change? It is my fault because I merged it without realizing that the feature was rejected.

@mdlinville
Copy link

I can't revert #369 cleanly so I'll just merge this one, which effectively does the same thing.

@mdlinville mdlinville merged commit 144f9ab into docker:vnext-engine Feb 3, 2017
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.

2 participants