Repository navigation
chore: Follow-ups to the containerdebug log collection - #892
Merged
Merged
Conversation
15 tasks done
NickLarsenNZ
previously approved these changes
Nov 9, 2026
NickLarsenNZ
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Follow-ups to #888, which collected the containerdebug logs.
Create the containerdebug log directory before containerdebug starts. Setting
FILE_LOG_MAX_FILESenables the pruning of old log files in the telemetry library, and that pruning runs before the first file is created. On a fresh Pod it therefore reads a directory which does not exist yet, and every container start printedThe message is harmless, because the appender creates the directory together with the file right afterwards, but it reads like a failure. The
mkdirreads$FILE_LOG_DIRECTORYrather than the path, so anenvOverridesentry for that variable creates the directory which containerdebug actually writes to. It is added incontainer_debug_command(), whose lines the callers join with"\n", so all roles are covered at once.Two smaller things in the same area: the value of
FILE_LOG_DIRECTORYis now derived fromSTACKABLE_LOG_DIRwithconcatcp!instead of being formatted at run time, and the comment on the log volume size limit is shortened to the two facts that matter.Part of stackabletech/issues#909
Definition of Done Checklist
Author
Reviewer
Acceptance
type/deprecationlabel & add to the deprecation scheduletype/experimentallabel & add to the experimental features tracker