You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of docker are you running? Docker version 17.09.0-ce, build afdb6d4
What version of registrator are you running? v7
Did you build a custom version of registrator? If so, what is that image? No. Using docker hub's latest.
What is the exact command you are running registrator with? docker-compose group with command set to -internal -tags zerotier -ip fcf0:a9af:17a3:c742:eb37::1 consul://localhost:8500
What is the exact command you are running your container with? Irrelevant for this issue
Description of the problem: Registrator is putting IPv4 addresses into my backend instead of IPv6 addresses.
I am trying to use Zerotier's 6PLANE networking for my docker containers and so I've disabled routing for IPv4 addresses. However, docker still assigns one and that is the one registrator is picking.
I thought that setting -ip to my host's IPv6 address would do it, but the registered addresses are still my IPv4 addresses. Am I missing something or is this not currently possible? Maybe I can tell docker to not assign an IPv4 address and then registrator wouldn't see it, but I haven't seen any way to do that either.
The text was updated successfully, but these errors were encountered:
-internal -tags zerotier -ip fcf0:a9af:17a3:c742:eb37::1 consul://localhost:8500
Description of the problem: Registrator is putting IPv4 addresses into my backend instead of IPv6 addresses.
I am trying to use Zerotier's 6PLANE networking for my docker containers and so I've disabled routing for IPv4 addresses. However, docker still assigns one and that is the one registrator is picking.
I thought that setting
-ip
to my host's IPv6 address would do it, but the registered addresses are still my IPv4 addresses. Am I missing something or is this not currently possible? Maybe I can tell docker to not assign an IPv4 address and then registrator wouldn't see it, but I haven't seen any way to do that either.The text was updated successfully, but these errors were encountered: