Conversation
Since commit 0f8fc31, the bridge driver will try to load kernel module br_netfilter if the userland proxy is disabled. If it fails, we're in unknown territory, so it's treated as an error. At the very least, containers will not be able to access host ports mapped to other containers in the same network. Before that, and before commit 5c499fc delayed the module load until it was needed - it was loaded unconditionally, but errors were only logged. So, on systems where the module is not available, or could not be loaded/configured, no error was reported and things "worked" (as long as you didn't try to use something that didn't work). That behaviour has been useful to some. So, make it possible to ignore the problem by setting env var: DOCKER_IGNORE_BR_NETFILTER_ERROR=1 Signed-off-by: Rob Murray <[email protected]> (cherry picked from commit e7bd60e) Signed-off-by: Sebastiaan van Stijn <[email protected]>
robmry
approved these changes
Jan 20, 2025
Contributor
robmry
left a comment
There was a problem hiding this comment.
Oh, thank you for doing this! LGTM.
1 task
This was referenced Mar 29, 2025
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.
Add a workaround for users wanting to run with
br_netfilterunloaded when it's needed.Since commit 0f8fc31, the bridge driver will try to load kernel module br_netfilter if the userland proxy is disabled. If it fails, we're in unknown territory, so it's treated as an error. At the very least, containers will not be able to access host ports mapped to other containers in the same network.
Before that, and before commit 5c499fc delayed the module load until it was needed - it was loaded unconditionally, but errors were only logged.
So, on systems where the module is not available, or could not be loaded/configured, no error was reported and things "worked" (as long as you didn't try to use something that didn't work).
- How I did it
That behaviour has been useful to some. So, make it possible to ignore the problem by setting env var:
DOCKER_IGNORE_BR_NETFILTER_ERROR=1.- How to verify it
br_netfilterand moved asidebr_netfilter.koso that it couldn't be reloaded"userland-proxy": falseexport DOCKER_IGNORE_BR_NETFILTER_ERROR=1- Description for the changelog