What problem will this feature address?
Hello, I've encountered some issues while trying to deploy Dokploy and set up CloudflareD on a ZimaOS machine (a Buildroot-based image), which lacks the CONFIG_IP_VS_PROTO_TCP and CONFIG_IP_VS_PROTO_UDP kernel features. Because of this, VIP mode in Docker does not work correctly, and it cannot resolve IP addresses properly.
It requires manually switching to DNSRR mode when deploying Dokploy on the server, and using the tasks.<app>:<port> name for CloudflareD instead of <app>:<port> to bypass Docker’s internal load balancer. This likely has downsides, such as the inability to use multiple replicas or clusters due to IP resolution limitations, but it would still be useful to have this documented. I spent a few days trying to identify this issue.
Describe the solution you'd like
Add separate FAQ point to mention that Dokploy requires these features enabled at kernel level to be able to work with Docker's VIP mode
CONFIG_IP_VS
CONFIG_IP_VS_RR
CONFIG_IP_VS_PROTO_TCP
CONFIG_IP_VS_PROTO_UDP
CONFIG_IP_VS_NFCT
CONFIG_NETFILTER_XT_MATCH_IPVS
CONFIG_NETFILTER_XT_MARK
Describe alternatives you've considered
None, sadly. Probalby would require to have DNSSR with manual Traefik proxy, but it's quite hard to implement and will require a lot of infrastructure changes
Additional context
No response
What problem will this feature address?
Hello, I've encountered some issues while trying to deploy Dokploy and set up CloudflareD on a ZimaOS machine (a Buildroot-based image), which lacks the
CONFIG_IP_VS_PROTO_TCPandCONFIG_IP_VS_PROTO_UDPkernel features. Because of this, VIP mode in Docker does not work correctly, and it cannot resolve IP addresses properly.It requires manually switching to DNSRR mode when deploying Dokploy on the server, and using the
tasks.<app>:<port>name for CloudflareD instead of<app>:<port>to bypass Docker’s internal load balancer. This likely has downsides, such as the inability to use multiple replicas or clusters due to IP resolution limitations, but it would still be useful to have this documented. I spent a few days trying to identify this issue.Describe the solution you'd like
Add separate FAQ point to mention that Dokploy requires these features enabled at kernel level to be able to work with Docker's VIP mode
Describe alternatives you've considered
None, sadly. Probalby would require to have DNSSR with manual Traefik proxy, but it's quite hard to implement and will require a lot of infrastructure changes
Additional context
No response