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.
Today whenever we run
crictl
, it generates several log files under/tmp
:This becomes a problem if we run the command in a loop, e.g. we run
crictl
every 10 seconds to check containerd healthness https://github.com/containerd/cri/blob/master/cluster/health-monitor.sh#L43.This can eventually fill the tmp directly. I do believe no one looks at those log files, and most people just read stderr.
Actually,
crictl
doesn't even have flags for glogs:Let's just always set
logtostderr=true
.Signed-off-by: Lantao Liu [email protected]