Remove broken config for IPv4 + IPv6 setup #3
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
While using the container in a dual-stack setup I noticed that it's sufficient to bind the IPv6 ports, as IPv4 traffic will reach the application as a translated IPv6 message. Thus using the IPv6-only config actually works for both IPv4 and IPv6.
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.
While using the container in a dual-stack setup I noticed that it's sufficient to bind the IPv6 ports, as IPv4 traffic will reach the application as a translated IPv6 message. Thus using the IPv6-only config actually works for both IPv4 and IPv6.