-
Notifications
You must be signed in to change notification settings - Fork 653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support basic IPv6 #3780
base: main
Are you sure you want to change the base?
Support basic IPv6 #3780
Conversation
I think we can not just upgrade the existing network. Properly we have to create a function that user can call which disconnect all container and recreate the network. This can be later also used if we allow to change the IP address of internal network |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can not just upgrade the existing network. Properly we have to create a function that user can call which disconnect all container and recreate the network. This can be later also used if we allow to change the IP address of internal network
Yea this is the only thing. In theory we could do this automatically but that could be pretty disruptive. Perhaps better to make a repair that does this?
Yeah, I will create the function and create an issue/fix about it and then we can merge it |
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
@pvizeli is there anything I might be able to do in order to help this PR move forward? I have built an addon that would benefit greatly from being able to get a working v6 address :) |
Can you elaborate a bit more on the use case for IPv6 in your add-on? The intention here is to assign an address from the ULA range. Depending on use case this might not be useful. |
Sure thing, my addon is just a simple packaging of the Bind DNS server. A lot of the major DNS registrars/clouds have v6 addresses for their DNS servers and it would be good to be able to reach those as well as the v4 addresses. FWIW ULA addressing is fine for this sort of thing in Docker because, as with v4, it sets up NAT for outbound connections on v6. |
Just a question, could this new feature be able to fix the issues I'm experiencing in my dual-stack network with the Add-ons? For example, I've not been able to configure access policies on NPM to work properly, since all traffic that is coming from IPv6 will seem to be coming from the bridge ( I know that I could easily disable dual-stack globally and run IPv4 only, but I'm starting a networks course next month and dual stack looks like it could be a great playground for my experiments (my ISP was kind enough to give me a static public IPv4 and a static /48 prefix for free). |
Proposed change
That is still not enough for full ipv6 support as we need the IPv6 plugin for handling the iptables correctly like we have IPv4 support until docker get full support of that and not like now, only partial
Type of change
Additional information
Checklist
black --fast supervisor tests
)If API endpoints of add-on configuration are added/changed: