No DNS for containers with untagged images about skydock HOT 4 OPEN

+1

from skydock.

I also hit this issue today... if it's not solvable I really suggest that we can also resolve containers by just using the {name}.{environment}.{domain}

from skydock.

Perhaps it's also my issue. I have a private repository somewhere on the network. If I run a container like this:

docker run -it -d --name myname docker:5000/library/myimage

I don't get the container added to DNS. If on the other hand I run it with a tag:

docker run -it -d --name myname docker:5000/library/myimage:latest

It gets added to the DNS.
Perhaps it has something to do with the colon symbol in the container name?

from skydock.

I think we just hit this too. Running with pre-built and tagged images from a private Docker Hub registry works just fine, but if we switch those images out for local ones we get the failure. The pre-built images were built using the exact same Dockerfile as the live builds.

from skydock.