Disable disk utilization check by default #850
Merged
Conversation
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
ikreymer
added a commit
that referenced
this pull request
Jun 16, 2025
cli: regen cli docs to update from #850
Merged
ikreymer
added a commit
that referenced
this pull request
Jun 16, 2025
cli: regen cli docs to update from #850
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.
Related to #848
Several users have had issues with disk utilization checks, including the values reported by
dfinside the crawler container having unexpected results for mounted volumes. The commonly recommended solution to this is to usedocker system ps, but that is of course not available within the Docker container itself.This PR changes disk utilization checks to be an opt-in feature by setting the default value to
0(disabled).