README: document default CNI paths and non-standard setup guidance#136
Closed
66Ton99 wants to merge 1 commit intocontainerd:mainfrom
Closed
README: document default CNI paths and non-standard setup guidance#13666Ton99 wants to merge 1 commit intocontainerd:mainfrom
66Ton99 wants to merge 1 commit intocontainerd:mainfrom
Conversation
Author
|
Related context:
|
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.
Summary
This updates the README to explicitly document the built-in default plugin/config directories and add guidance for non-standard environments.
Changes
WithPluginDirandWithPluginConfDirare not providedWhy
The defaults are currently implicit in code and easy to miss. Making them explicit in documentation helps users avoid confusing runtime setup issues when system-wide directories are not present or writable.
Review request
I would appreciate review from someone familiar with both
go-cniand real-world runtime setups (including Darwin/rootless environments) to confirm this guidance is accurate and helpful.