unrecognized adapter: consul-tls://

[ryansmithevans]

• What version of docker are you running? 1.13.1
• What version of registrator are you running? v7
• Did you build a custom version of registrator? If so, what is that image? no
• What is the exact command you are running registrator with?

docker run --net host -e CONSUL_CACERT=/consul/ssl/ca.crt \
 -e CONSUL_TLSCERT=/consul/ssl/consul.agent.crt \
 -e CONSUL_TLSKEY=/consul/ssl/consul.agent.pem \
 -v /var/run/docker.sock:/tmp/docker.sock \
 -v /certs/consul_agent:/consul_agent/ssl:ro \
 --name registrator gliderlabs/registrator:v7 \
 -ip=<ipaddress> -cleanup -ttl 120 -ttl-refresh 30 -resync 60 \
 consul-tls://consul.agent.internal:8500

• A log capture of all the docker events before, during, and after the issue.

 2017/03/30 09:44:14 Starting registrator v7 ...
 2017/03/30 09:44:14 Forcing host IP to <removed>
 2017/03/30 09:44:14 unrecognized adapter: consul-tls://consul.agent.internal:8500

Description of the problem:

Unable to run registrator with TLS , getting an unrecognized adapter error for consul-tls.

[rgruyters]

Same here. I'm using the following command:

docker run -d \
    --name=registrator \
    --net=host \
    --volume=/var/run/docker.sock:/tmp/docker.sock \
    --volume=/etc/pki/node:/etc/ssl/node \
    -e CONSUL_CACERT=/etc/ssl/node/ca.crt \
    -e CONSUL_TLSCERT=/etc/ssl/node/server.crt \
    -e CONSUL_TLSKEY=/etc/ssl/node/server.key \
    gliderlabs/registrator:latest \
    consul-tls://<<consul server fqdn>>:8500

[josegonzalez]

This functionality is currently only available via master, not with the latest v7 release.