host-ctr: exposes error level log messages to console #479
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available: Fixes #477
Description of changes:
Splits logrus logs to different output with LogSplit logrus hook.
Error, fatal, panic levels goes to standard error and all other log levels go to stdout
Testing:
Locally ran
host-ctr
with an invalid image repository:Then with valid image repository:
Verified that errors get written to stderr and everything else to stdout:
On a Thar instance with the following in userdata:
[email protected]
outputs error messages to the console:By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.