Predictable DNS name and hostname in swarm

[sgas]

Hi, I am wondering about the current naming scheme in swarm.  The hostname  choosen is the container-id . The DNS  name for a container has a  random and hence unpredictable post-fix.   For example as follows. 

DNS Name :  astest.1.dn0dsyxci7s5u7vf8k7238upm

hostname:  88c2a48c1795  

1.  Is there any benefit  of setting  the DNS name and hostname different  in this case  ?    It would be good to have an option to make them the same

2.  The DNS name seems to have 2 parts  - the prefix part  , <service name>.index,  and  the postfix part,  a hash  .    The hash  makes the container names  difficult to  predict and hence automate .   Is there a way the postfix part can be made predictable (e.g. not have the postfix , etc.) ?

[santho...@docker.com]

Hi,

Since a service can have multiple tasks running on the same node, the container name has a taskid component to make it unique. Do you have a specific requirement to use the container names ? You can get all the backing container IPs by doing a DNS lookup on "tasks.service_name".

-Santhosh.

[Madhu Venugopal]

There is also this : https://github.com/docker/docker/pull/24973

-Madhu

--
You received this message because you are subscribed to the Google Groups "docker-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to docker-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sgas]

Hi,    some apps use/require dns names unfortunately  rather  than IPs.    Also hostname  and dns name requires to be aligned for some applications to work correctly.

To unsubscribe from this group and stop receiving emails from it, send an email to docker-dev+...@googlegroups.com.