April 19, 20233 yr I have docker setup using ipvlan and have a couple basic websites. I have the docker containers using real world ipv6 addresses as my ISP support full ipv6 and I give my docker containers a global ipv6 address, punch a hole in the fire wall and then anyone on ipv6 can access them. However I installed cloudflared docker container (As guided on in my cloudflare profile) to create a tunnel and cloudflare has put in either a route or an interface, I'm not 100% sure, but the ipv6 address belongs to cloudflare. So my ipv6 range that my ISP statically assigned to me starts with 2404: the range cloudflare added starts with fdd7: I restarted my server and now docker will bind to the fdd7: ipv6 address and not the 2404: address, meaning some of my containers fail to start due to them being setup in tied to the br0 interface with a static ipv6 address starting with 2404: and not having access to it. Deleting the cloudflare tunnel keeps the fdd7: ip route in place even after rebooting the server and I cannot get docker to bind to the 2404: ip range. I would like to use the cloudflare tunnel but keep docker binded to 2404: Note: It all worked before I rebooted. I had docker containers on 2404: ip ranges running across the cloudflare tunnel and it was all working. I'm still learning about docker and my only real experience is in unraid, which I know is kinda different from a "standard" docker install so if there is command I need to run in the unraid console I will need a little extra help on that. eevee-diagnostics-20230419-1125.zip Edited April 19, 20233 yr by ziogref spelling
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.