Closed Vahor closed 1 week ago
https://github.com/coollabsio/coolify/issues/2495 can also be a solution, adding a custom network with ipv6 and using this one will solve my problem. Edit: we'd still have to enable the ipv6 support on docker
This is an improvement request as it has not yet been implemented, so I am moving this to a GitHub discussion - the other issue is slightly different and has a bounty so I can not move it.
Description
I need to access the ipv6 of an app running in a container. But the network does not seem to be able to access those ips.
I can delete the
coolify
network and recreate it with ipv6 support but as it's also managed by coolify it seems hacky and doing so on every server does not seem nice. (That's what I'm currently doing)Doc is not very clear about what the flag does, but I also tried with
--ip6
, it does not change anythingMinimal Reproduction (if possible, example repository)
Inside a container using the coolify network or
docker run --rm -it --network coolify ubuntu
You'll see an error
(works for ipv4)
Note: or simpler by installing
net-tools
and runningifconfig
, you'll see that with coolify network you don't have the inet6, but without the coolify network an address is here.For comparison, you can run a container using the host network
docker run --rm -it ubuntu
. Same commands, here it woks.Exception or Error
No response
Version
v4.0.0-beta.323
Cloud?