-
-
Notifications
You must be signed in to change notification settings - Fork 71
install.sh: Add compatibility with end-to-end IPv6 #59
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
base: main
Are you sure you want to change the base?
Conversation
Installing Server Dependencies: ✅ I am completely unable to connect dokploy via ipv6 directly, although from console I connect locally (using proxy with ipv6 connection support) as my ISP doesn't support ipv6 connection by default, but via terminal client + socks5 proxy I can easily access my vps via ipv6. Please fix Dokploy to work over ipv6 connection check #2509 (Dokploy/dokploy#2509) |
|
I don´t think this part is related to this PR, it looks like you cannot connect over SSH which has nothing to do with this PR and have to be taken care on the server OS directly. |
|
Did you actually test if this works? I tried these changes and IPv6 traffic did not work properly. After doing some research it seems that docker swarm itself still has no proper IPv6 support. |
|
Yes I am using it on my dokploy infra and it's working fine. (On my case it's a single node dokploy setup, I think for multi-nodes setup there are also some nodejs code to update to run docker API calls with the proper parameters for dual stack) You can try by yourself: |
|
Yeah I have a multi-node setup that's probably it, gotta look into that. Thanks |
|
I remember when taking a look there were some part of the NodeJS that would do the equivalent of what I did with the install script but I did not modify them yet as I don't have any multi-nodes setup to test it |

Update
install.shto configure all internal network as dual stack.This allow to have true end to end IPv6 connectivity whenever possible, this allows for example IPv6 clients to reach IPv6 backend without losing the original source IPv6 in the process.
Fixes Dokploy/dokploy#2349 (comment)
There may have others changes to reflect if any part of the code also creates IPv6 (in clusters mode for example, I don´t have any cluster to test this part), but basically the only change that would be needing to these calls would be to create the new networks as dual stack (equivalent of
--ipv6 --ipv4of the cli command)