test_connect_with_ipv6_address: enable IPv6 #3372
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
Signed-off-by: Rob Murray <rob.murray@docker.com>
akerouanton
approved these changes
Nov 24, 2025
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.
test_connect_with_ipv6_addresscreates a network with IPv6 IPAM, and checks it's possible to start a container with a configured IPv6 address ... but it doesn't enable IPv6 in the network.The test passes because the daemon checks the configured IPv6 address is in a configured subnet - and it is, but the IPv6 subnet wasn't used. So, the IPv6 address isn't assigned to an interface in the container, it just appears in its config.
moby/moby#51577 updates the daemon to check the network is using a subnet containing the configured address - so this test will fail.