Registrator setting wrong service names with consul, breaking DNS resolution

[zd-carmo]

• What version of docker are you running? 1.11.2, build 4dc5990
• 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? -resync=300 consul://127.0.0.1:8500
• What is the exact command you are running your container with?
• A log capture of all the docker events before, during, and after the issue.
• If relevant, Dockerfile for application that is having issues.

Description of the problem: When a container is brought up by referring to the image based on the SHA256 value instead of the label (so, /@sha256: instead of /:), Registrator registers the service with consul with the name "@sha256". The problem here is that this ends up breaking DNS discovery, as the '@' character is not valid in DNS.

How reproducible: Every time that the above situation is done.

Steps to Reproduce: a) Bring up a container by referring to the image by sha value. b) Check that the service got registered with the wrong name.

Actual Results: Service gets registered with name "@256"

Expected Results: Service gets registered with name ""

Additional info:

[zyndaras]

@zd-carmo:

You can override the service name (among other attributes) by providing a label to the container you want registered in the docker run command: --label "SERVICE_NAME=some-service-name"

or if you're using Compose v2 you can add:

labels:
  - "SERVICE_NAME=some-service-name"

Although it doesn't apply to your version, in case you upgrade to Docker 1.12+ swarm-mode services you'll need to add the following option to docker service create command: --container-label SERVICE_NAME=some-service-name

More details can be found in the service model documentation

Give it a try and let me know if it works!

[alexinthesky]

I had the same issue with docker 17.03. seems to be fixes with swarm mode and docker version 17.04.

A