-
Notifications
You must be signed in to change notification settings - Fork 642
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
Enhancement: add log-driver capability to docker:run #379
Comments
at some point, yes. pull requests welcome... |
Ok, I've got it working now locally. After some cleanup I will make a pull request. |
Cool. Looking forward to the PR ;-) |
Closed
Finally made a pull request: #387 |
Thanks ;-) 'will have a look at it ASAP |
rhuss
added a commit
that referenced
this issue
Feb 24, 2016
This is based on PR #387 with the following changes: * Moved driver config to the overall LogConfiguration in the run section. Although its not directly related, having two different logging configuration sections is even more confusing. * Adapted documentation * Added unit tests * Added missing log configuration properties to the PropertyHandler.
Merged, should be available in 0.14.0 (to be released in this week) |
Thanks, tested the latest release from maven central and it works as expected. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I could not find any support for using a different log-driver within docker:run.
For some containers we use the gelf log driver in docker:
sudo docker run -d --log-driver=gelf --log-opt gelf-address=udp://localhost:12201 myimage
Any plans to add this?
The text was updated successfully, but these errors were encountered: