support .conflist CNI configs - #3029
Merged
Merged
Conversation
Signed-off-by: Alex Suraci <suraci.alex@gmail.com>
tonistiigi
approved these changes
Aug 16, 2022
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
2 participants
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.
👋 I'm using Buildkit's CNI support in a project of mine and found that I need to additionally configure the
firewallplugin, otherwise starting Docker seems to break network connectivity.Configuring this plugin requires me to switch to a "chained CNI config" which is a special type of config:
.conflistin order forcnitoolto recognize it as onego-cniusingcni.WithConfListFilerather thancni.WithConfFileI opted to double down on
cnitool's behavior here to keep the distinction from bubbling up to separate fields inbuildkitd.toml, but I'm happy to do that instead.