chore(tests): Future-proof whitelist against Docker network changes#9500
Merged
mangalaman93 merged 1 commit intomainfrom Sep 8, 2025
Merged
Conversation
github-actions
Bot
added
area/testing
mangalaman93
deleted the
matthewmcneely/whitelist-update-for-test-artifacts
branch
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.
Description
This PR changes the security/whitelist superflag definition in docker compose files and other places where docker cmds are issued. The change is to the "all ipv4 addresses" CIDR definition (0.0.0.0/0).
Background: after updating Docker on my Mac, clients presented a new 175.x ip address that was not covered by the old set of CIDR definitions.
Checklist