Skip to content
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

Possible to force registrator to use IPv6 instead of IPv4? #598

Closed
BlinkyStitt opened this issue Oct 14, 2017 · 2 comments
Closed

Possible to force registrator to use IPv6 instead of IPv4? #598

BlinkyStitt opened this issue Oct 14, 2017 · 2 comments

Comments

@BlinkyStitt
Copy link

  • 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.

@BlinkyStitt
Copy link
Author

BlinkyStitt commented Oct 16, 2017

I think I've figured out the right places to change: BlinkyStitt@2f70361
BlinkyStitt@e3501f2

This commit works for me, but isn't something that makes much sense to merge here.

Any suggestions on the best way to support both IPv4 and IPv6?

@BlinkyStitt
Copy link
Author

My first search missed this somehow. #229

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant